Combined with work experience, write this article, all dry goods and experience sharing. Use your 5 minutes to finish reading, I hope to help you!
White box testing
White-box Testing (also known as logic-driven Testing, structural Testing), it is to know the internal working process of the product, through Testing to detect whether the internal action of the product is carried out normally in accordance with the specifications, according to the internal structural Testing procedures of the program, Verify that each path in the program has the capability to work correctly as intended, regardless of its functionality.
Support for development language: white box testing tool is to test the source code, the main content of testing includes lexical analysis and grammar analysis, static error analysis, dynamic detection, etc. At present, the test tool mainly supports development languages including standard C, C++, Visual C++, Java, Visual J++ and so on.
The main methods of white box testing include logic driving, basic path testing and so on, which are mainly used for software verification. The “white box” method comprehensively understands the internal logical structure of the program and tests all logical paths. The “white box” method is an exhaustive path test.
White-box testing of software is a careful examination of the procedural details of software. This method regards the test object as an open box, which allows testers to design or select test cases by using the logical structure and related information inside the program to test all the logical paths of the program. Determine whether the actual state is consistent with the expected state by checking the program state at different points. Therefore, white box testing is also called structural testing or logic-driven testing. A white-box test is intended to check the program modules as follows:
1. Test all independent execution paths of the program module at least once. 2, for all logical decisions, take “true” and “false” two cases can be tested at least once. Execute the body of the loop within the bounds of the loop and within the bounds of the run. 4. Test the effectiveness of internal data structures, etc.
Black box testing
Definition: The black box test method treats the program as a black box, completely ignoring the internal structure and processing of the program; A black box test is performed outside the program to check whether the program function is working as specified in the specification. Black box testing is also called functional testing.
Black-box testing of software means that testing takes place at the interface of the software. In this method, the test object is regarded as a black box. The tester does not consider the logical structure and internal characteristics of the program at all, but only checks whether the function of the program conforms to its function description according to the requirements and specifications of the program. So black box testing is also called functional testing or data driven testing. Black box tests are designed to detect the following types of errors:
1. Are there any incorrect or missing functions? 2. On the interface, can input be correctly accepted? Can the output be correct? 3. Is there any data structure error or external information (such as data files) access error? 4. Can the performance meet the requirements? 5. Are there initialization or termination errors?
Difference between white box and Black Box Any engineering product can be tested using one of two methods.
Black box testing: given the functional design specifications of the product, tests can be carried out to prove that each implemented function meets the requirements.
White box test: the internal working process of the product is known. The test can prove that each internal operation conforms to the design specification and all internal components have been inspected.
White boxes and black boxes
The initial test focuses on each module to ensure the correctness of the source code, and this stage becomes the unit test, mainly using the white box test method.
Next comes module integration and integration to form complete packages. Integration testing focuses on validation and program composition, mainly using black box testing method, supplemented by white box testing method.
10G mass software testing related information, video, tools waiting for you to get
Baidu cloud access information point he 👉 link: extraction code: ESyd
The static test
Testing software by running programs is called dynamic testing. Testing software by reviewing documents, reading code, and so on is called static testing. In dynamic testing, white-box testing and black-box testing are often used to design test cases from different angles to find errors in software code.
Static test method means that the test program itself is not run, only by analyzing or checking the syntax, structure, process, interface of the source program to check the correctness of the program. Make structural analysis, flow chart analysis, symbol execution to find errors in requirement specification, software design specification and source program.
The static method analyzes the static characteristics of the program to find flaws and suspicions, such as mismatched parameters, improper loop nesting and branch nesting, disallowed recursion, unused variables, null pointer references, and suspicious calculations.
Static test results can be used for further error detection and provide guidance for test case selection.
Regression testing
It is a test strategy and method to ensure the original function is normal when the program is modified. In plain English, when we test the program, we find a bug and then return it to the programmer for modification. After modification, the programmer releases a new software package or a new software patch package to our tester. We have to test the program again to ensure that the program runs normally under the condition that the previous bug is corrected. A process that does not introduce new errors. In general, comprehensive testing is not required, but rather effective testing based on modifications.
10G mass software testing related information, video, tools waiting for you to get
Baidu cloud access information point he 👉 link: extraction code: ESyd
How to classify the defect level of software?
1. Fatal error, which may cause the module and other related modules to be abnormal, crash and other problems; 2. A serious error occurs. The problem is limited to this module, resulting in module function failure or abnormal exit; 3. General error, module function part failure; 4. Suggest questions and propose the improvement suggestions for the test object.
Phase of software testing
Unit testing
Is a test of the basic building blocks of software, such as a module, a process, etc. It is the most basic and important part of software dynamic testing, and its purpose is to check the correctness of the basic components of software.
Unit testing is the lowest level of testing activities to be carried out in the process of software development. In unit testing activities, independent units of software are tested in isolation from other parts of the program. The test focuses on the modules of the system, including the correctness verification of subroutines.
Integration testing
It is a test carried out in the process of software system integration. Its main purpose is to check whether the interface between software units is correct.
Integration testing, also called assembly testing or joint testing. On the basis of unit test, all modules are assembled into subsystems or systems according to design requirements for integration test. Practice shows that although some modules can work independently, they cannot be guaranteed to work properly when connected together. Some problems that cannot be reflected in some parts of the program are likely to be exposed globally and affect the implementation of functions. The test focuses on the connection between modules and the transfer of parameters.
The system test
It is to assemble the tested subsystems into a complete system for testing. It is an effective way to verify that the system can indeed provide the functionality specified in the system solution specification. The test focuses on the operation of the whole system and the compatibility with other software.
The integrated software system is thoroughly tested to verify the correctness and performance of the software system to meet the requirements specified by its specifications. It is not a simple task to check whether the behavior and output of the software are correct, which is called the “foreknowledge problem” of testing.
The acceptance test
Is to show the purchaser of the software that the software system meets the needs of its users. Its test data is usually a subset of system test data.
The above suggestions are for reference only! [Lebo Software Testing] [Lebo College]
If there is infringement please contact delete