Different documents use in testing
In SDLC, when the requirement is given the developer is busing in coding and test engineer is busying in writing test documents in this session I am going to explain different phases use in testing any application.
Test documents(Different documents use in testing)
These are necessary notes or the reference documents which are prepared by the test engineer simultaneously. when a developer is busing in coding.
These documents are written so that they can be used for any future reference while performing the test execution process.
Importance of test document
In a test document whatever we plan, we write, so that we can’t forget any scenario
(Different documents use in testing)
when the test engineer leaves the company and when the new test engineer comes .we can refer to him so that they proceed for testing without see the requirement and it also save the time.
Test Scenario (Different documents use in testing)
It is high-level documents written by test engineer which talks about all possible combinations or multiple ways of testing the application and generally this document is written to understand the flow of the application.
NOTE: Rules to be followed while writing test scenarios.
- Always pick module by module shows that a proper sequence is maintained.
- Every scenario should be written in one or max of two-line so that it is easy to understand.
- Every sentence should consist of doing and checking.
Test Cases(Different documents use in testing)
It is an in detail documents which talk about step by step procedure to test an application. The test cases consider all possible scenarios, navigation step, and inputs which need to be tested for application. These documents can be referred by any person who wants to check the application.
Test Case Templates(Different documents use in testing)
In order to start the writing, the test cases we should have test case templates to maintain informality.
The scenario should be derived to understand the flow of the application and we should refer back to the requirement to write the input.
Test Execution Process
Once the test cases are written received or approved and the test engineer is sure that it does not consist of any mistake then we start the test execution process.
In this process, we start testing the application by executing the test.
NOTE; Status of the test cases.T
- Pass: When all the steps of the test cases are working as expected then the status is a pass.
- Fail: When any of the steps of test cases does not work as expected then the status is failed.
- Partial: Whenever when all major steps of the test cases are working as expected and any of the minor steps are not working such cases the status can be called partial.
Test Cases Design Technique
These are design techniques or methods that need to be followed by test engineers while writing test cases to achieve maximum test coverage.
The different test case design technique are:
- error guessing: In this type, the test engineer starts guessing the values based on the assumption of requirement.
- equivalence partition: whenever the requirement is a range of values then derive test cases for one valid value and two invalid inputs.
- general partition methods: whenever the requirement is range+criteria divide that range into intervals based on criteria and check for all those values.
NOTES: Depending on the requirement we decide which test case design technique needs to used to write the test case.so that maximum test coverage will be achieved.