A test script is a set of instructions in software testing that will be performed on the system under test. Testing is done to check whether the system functionality is as expected. It is chronological steps to validate a test case.
What are the different test design techniques?
Software testing Techniques help you design better cases. While increasing test coverage testing techniques help reduce the number of test cases to be executed since exhaustive testing is not possible. They help identify test conditions which are difficult to recognize.
Black box testing techniques are:
1) Boundary Value Analysis (BVA)
- Boundary Value Analysis is used to test the values at the boundaries of allowed data.
2) Equivalence Class Partitioning
- Equivalence partitioning helps us to reduce the number of test cases to write. Because all the values are handled exactly in the same way so we need to test one partition among them.
3) Decision Table Based Testing
- Decision table helps us to define what the system should do. They are rules which work in combination for this testing. It helps us to manage the complexity of each combination of possibilities visible so that we can decide whether and how to test it.
4) State Transition
- State Transition Testing is helpful when a testing have series of stable situations. A set of rules that decides which situation it can go depending on which one it’s in now.
5) Error Guessing
White box testing techniques are:
- Statement coverage
- Decision coverage
- Condition coverage
- Decision-condition coverage
- Multiple condition coverage
- Basis Path Testing
- Loop testing
- Data flow testing
What is traceability matrix?
- All requirement’s proposed by the clients are captured by requirement traceability matrix or RTM.
- In other words it is a document traces user requirement with test cases.
- The main purpose of requirement traceability matrix is while doing software testing no functionality should miss it helps us to cover all the test cases.
What is the difference between regression and retesting?
Differences between Retesting and Regression Testing:
- To verify defects we found previously and fix them to work correctly is done in retesting, on the other hand, we perform regression testing to check when the defect is fixed and it has not affected other functionality which was working fine before making changes in the code.
- Retesting is specifically performed when the defect is fixed where as in regression testing is not about specific to any defect fix .Regression testing is performed when any bug is fixed.
- Retesting execute those test cases that are failed earlier whereas regression test execute test cases that was passed in earlier builds.
- Regression testing has lower priority over retesting.
Click here for MCSE Certification.