Important Terms in Software Testing
Important Terms in Software Testing
A bug which needs to handle as a high priority bug and fix it immediately.
- Boundary Value Analysis
Boundary value analysis (BVA) is based on testing the boundary values of valid and invalid partitions. The Behavior at the edge of each equivalence partition is more likely to be incorrect than the behavior within the partition, so boundaries are an area where testing is likely to yield defects. Every partition has its maximum and minimum values and these maximum and minimum values are the boundary values of a partition. A boundary value for a valid partition is a valid boundary value. Similarly, a boundary value for an invalid partition is an invalid boundary value.
- Equivalence Class Partition
Equivalence Partitioning is also known as Equivalence Class Partitioning. In equivalence partitioning, inputs to the software or system are divided into groups that are expected to exhibit similar behavior, so they are likely to be proposed in the same way. Hence selecting one input from each group to design the test cases.
- Decision Table testing
Decision Table is aka Cause-Effect Table. This test technique is appropriate for functionalities which has logical relationships between inputs (if-else logic). In Decision table technique, we deal with combinations of inputs. To identify the test cases with decision table, we consider conditions and actions. We take conditions as inputs and actions as outputs.
- State Transition
Using state transition testing, we pick test cases from an application where we need to test different system transitions. We can apply this when an application gives a different output for the same input, depending on what has happened in the earlier state.
- Entry criteria
The prerequisites that must be achieved before commencing the testing process.
- Exit criteria
The conditions that must be met before testing should be concluded.
Software Development Life Cycle (SDLC) aims to produce a high-quality system that meets or exceeds customer expectations, works effectively and efficiently in the current and planned information technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.
- Can you do System testing at any stage of SDLC?
We can do System Testing only when all the units are in place and working properly. It can only be done before User Acceptance Testing (UAT).
- Procedure of manual testing
Manual testing is crucial for testing software applications more thoroughly. The procedure of manual testing comprises of the following.
- Planning and Control
- Analysis and Design
- Implementation and Execution
- Evaluating and Reporting
- Test Closure activities
STLC (Software Testing Life Cycle) identifies what test activities to carry out and when to accomplish those test activities. Even though testing differs between Organizations, there is a testing life cycle.
Requirements Traceability Matrix (RTM) is used to trace the requirements to the tests that are needed to verify whether the requirements are fulfilled. Requirement Traceability Matrix AKA Traceability Matrix or Cross Reference Matrix.
- Test Metrics
Software test metrics is to monitor and control process and product. It helps to drive the project towards our planned goals without deviation. Metrics answer different questions. It’s important to decide what questions you want answers to.
If you are someone who is interested in software testing, join QcMore, the most advanced software testing training institute in Kochi. There are many software testing training courses in Kochi, but what sets us apart is our curriculum that is a perfect blend of theory and practice with lectures and live projects. We also provide a combination of manual training and automation software testing training, so as to equip you with all necessary skills demanded by the industry