Learning Test day 2

eye mask test software (Dynamic black box test):
Universal Test and failure test: universal Testing is to identify what the software can do, rather than testing its capabilities. Use Cases designed purely to damage the software are called failure tests.
equivalence classification: selecting a software test case is the most important task of the tester. Equivalence classification refers to the reduction of test cases with massive data, but the process is equally effective.
the data volume is massive. To divide equivalence classes, follow the following principles: 1. boundary condition, 2. subboundary condition, 3. default, blank, null, zero and none, 4. illegal, error, incorrect, and junk data
Status test: the software status refers to the current condition or mode of the software. (The software Tester must test the Program status and its conversion)
logical process of the test software:
1. establish a state transition diagram (each independent state that the software may enter, from one state to another, requires the input and conditions, and sets the conditions and output results when entering or exiting a State)
2. reduce the testing status and the number of conversions
3. perform specific tests (design test cases)
how to test the failure status: competition conditions and time series disorder, repeat, compress, and overload
other black box testing technologies: Do the same for users, search for Software defects that have been found, consider issues like hackers, and rely on experience, intuition, and hunch

check if the Code is not running (static white box test):
: encoding standards and specifications (reliability, readability, portability), data reference errors, data declaration errors, calculation errors, and comparison errors, incorrect control process, subroutine, and input/output.
X-glasses test software (Dynamic white box test):
dynamic white-box testing is to determine which tests are required and which do not need to be tested by checking the information obtained from the code function (what is done) and implementation method (how to do it, how to expand the test.
segmentation test: A test at the underlying layer is called a unit test or a module test, which fixes underlying software defects, to test the combination of modules.

code coverage: 1. statement overwrite, 2. branch coverage, 3. condition overwrite
statement overwrite: each statement must be executed at least once.
branch overwrite: All paths must be overwritten.
conditional overwrite: overwrite each possible condition in a judgment statement.