It is carried out to test the program and its implementation in order to increase the efficiency or code structure. It is also known as “structural” testing.
White box testing
In this method of testing, the design and the structure of the code are known to the tester. Code programmers conduct this code test.
Below are some methods of testing the white box:
Testing the control flow. The purpose of testing the control flow to set up test cases covering all operators and branching conditions. Ridigns are checked both for truth and falsity so that all operators can be covered.
Testing data flow – this testing method focuses on all variable data included in the program. He checks where the variables were declared and determined and where they were used or changed.
Testing the control flow. The purpose of testing the control flow to set up test cases covering all operators and branching conditions. Ridigns are checked both for truth and falsity so that all operators can be covered.
Testing data flow – this testing method focuses on all variable data included in the program. He checks where the variables were declared and determined and where they were used or changed.
Testing levels
Testing itself can be determined at different levels of SDLC. The testing process is in parallel with the development of software. Before moving on to the next stage, the stage is checked, confirmed and checked.
Testing is separately carried out only to make sure that there are no hidden errors or problems in the software. The software is tested at different levels –
Modular testing
During coding, the programmer performs some tests on this program module to find out if he contains errors. Testing is carried out on the principle of a white box. Modular testing helps developers decide that individual program modules work in accordance with the requirements and do not contain errors.
Integration testing
Even if units of software work normally separately, it is necessary to find out whether the units united together will also work without errors. For example, the transfer of arguments, data updating, etc.
System testing
The software is compiled as a product, and then tested as a whole. This can be done using one or more of the following tests:
Checking functionality. Checks all the functionality of the software for compliance with the requirements.
Product testing – this test confirms the effectiveness of software. He checks the effectiveness and average time required by the program to complete the desired task. Performance testing is performed using load testing and stress testing, when the software is subjected to high loading user and data under various environmental conditions.
Safety and tolerance – these tests are carried out when the software is designed to work on various platforms and is available for several people.
Checking functionality. Checks all the functionality of the software for compliance with the requirements.
Product testing – this test confirms the effectiveness of software. He checks the effectiveness and average time required by the program to complete the desired task. Performance testing is performed using load testing and stress testing, when the software is subjected to high loading user and data under various environmental conditions.
Safety and tolerance – these tests are carried out when the software is designed to work on various platforms and is available for several people.
Accepting testing
When the software is ready to transfer to the client, it must undergo the last stage of testing, where it is checked for interaction with the user and response. This is important because even if the software meets all the requirements of the user and if the user does not like how it looks or works, it can be rejected.
Alpha testing. The development team independently performs alpha testing using the system as if it were used in the working environment. They try to find out how the user will respond to some actions in the software and how the system should respond to the input data.
Beta testing-after internal software testing, it is transmitted to users for use in the production environment only for testing purposes. This is not a delivered product. The developers expect users at this stage will bring minor problems that were missed to participate.
Alpha testing. The development team independently performs alpha testing using the system as if it were used in the working environment. They try to find out how the user will respond to some actions in the software and how the system should respond to the input data.
Beta testing-after internal software testing, it is transmitted to users for use in the production environment only for testing purposes. This is not a delivered product. The developers expect users at this stage will bring minor problems that were missed to participate.
Regression testing
Whenever the software product is updated with a new code, function or functionality, it is thoroughly tested to determine if there is any negative impact of the added code. This is known as regression testing.
Testing documentation
Test documents are prepared at different stages –
Before testing
Testing begins with the generation of test cases. The following documents are necessary for reference –
SGD document – a document on functional requirements
A document on testing policy – describes how far testing should be passed before the release of the product.
A document on testing strategy. Here, aspects of the testing team, the matrix of responsibility and law / liability of the testing manager and the test engineer are described in detail.
The tracking matrix document is a SDLC document related to the process of collecting requirements. As new requirements appear, they are added to this matrix. These matrices help the testers find out the source of the requirements. They can be traced forward and back.