Use Case Testing: The ISTQB syllabus expects the Software Tester at the Foundation level to understand and explain Use Case testing (K2 level). In contrast, the Software Tester has to apply the knowledge in selecting the test cases for the other Black Box techniques (Equivalence Partitioning, Boundary Value Analysis, Decision Table and State Transition – […]
Read MoreState Transition Testing Technique: This technique falls under the Black Box testing techniques and the ISTQB syllabus excepts the tester to 1. understand State Transition diagrams and State tables 2. derive test cases from the State Transition diagrams and State Tables 3. Sequences – shortest, longest sequences 4. Null or Invalid transitions 5. Chow’s switch coverage State-transition […]
Read MoreDecision Table Testing: Consider this from an vehicle insurance Functional Spec: If the age of the driver is greater than 25 and the driver is female, offer a discount of 10%. In Equivalence Partitioning and Boundary Value Analysis, the focus was on single or specific inputs and probably more focused on UI. And the techniques […]
Read MoreWhat is Boundary Value Analysis? Boundary value analysis is one of the best testing techniques in the software industry for testing software functions. It tests and detects if the software functions perfectly with the boundary values. The above technique tests values on, inside and outside particular boundaries. Testers detect major issues by analyzing the boundary […]
Read MoreEquivalence Partitioning: The word Equivalence means the condition of being equal or equivalent in value, worth, function, etc. The synonyms for the word are equal, same, identical etc. Equivalence Partitioning is a black box technique to identify test cases systematically and is often the first technique to be applied when designing test cases. Equivalence Partitioning […]
Read MoreBlack Box Techniques: These are test design techniques primarily used during System/Functional testing by the Testing team to design test cases. The word ‘BlackBox’ is key- the application under test(AUT) is treated as a Black Box or an opaque box, the tester is unconcerned about the internal working of the application. What the tester is […]
Read MoreISTQB Test Analysis and Design: In the ISTQB syllabus, the Test Process consists of a five phases Plan, Design, Implement/Execute, Report, Closure. (Our blog titled “Software Test Life Cycle” has more details .) The second phase of the Software Test Life Cycle is Test Analysis and Design, where specifications are analysed and test cases designed. This […]
Read MoreWhen we log defects there are two fields that we need to fill in – Severity and Priority. In this blog, we look at the differences between these and some typical scenarios. Defect Severity: This stands for the degree of impact the defect can have on testing and user’s needs. High – showstopper, tester/user cannot […]
Read MoreWe have seen the Software Development Life Cycle in one of our previous blogs. V-model, Iterative models are examples of how software can be developed. The Software Test Life Cycle is a part of the Software Development Life Cycle. And the Test Life Cycle is used for System Testing and for User Acceptance Testing. The […]
Read MoreDefects: Defects are the most visible part of the Software Test Process. Defects found in Production/Live environment and by customer are termed ‘Failures’. Any testing team is evaluated by the number found during testing and the failures encountered by the customer. If the customer encounters a vast number of failures, the efficacy of the testing […]
Read More
