Skip to main content

Strategies and methods for test case design II

Strategies and methods for test case design

Today we are talking about how to get an approach for writing a good test case. Developers cannot prevent or eliminate all the defects raised in the application during implementation. That's why the application should be tested before deliver to the customer.
Before starting the execution, we need to identify test scenarios and write test cases for each identified scenarios. Test case is test description which needs to be executed to verify the functionality or feature of the application. A good test case have a good possibility of finding defects.
For designing effective test cases, there are two basic strategies that can be used.
  1. Black box test strategies
  2. White box test strategies
08.png
Test StrategiesSourcesTesting Techniques
Black Box Functional requirement specificationEquivalence partitioning
 Business requirement specificationBoundary value analysis
 Domain knowledgeState Transition Testing
  Decision table
  Use case testing
  Error guessing
White BoxHigh level designStatement coverage
 Control flow graphDecision coverage
 Cyclomatic complexityCondition coverage
Black Box approach to test case design
As a foundation for designing black box test cases, we are mainly considering inputs and outputs . Testers should choose what are the possible valid and invalid inputs. Exhaustive testing is not possible. Exhaustive testing means testing with all possible inputs. Therefore the combination of different testing techniques are used to detect different types of defects. Sources such as functional requirement specification, business requirement specification and domain knowledge are used to determine test scenarios of application. Equivalence partitioning, Boundary value analysis, State Transition Testing, Decision table,Use case testing and Error guessing are testing techniques of black box testing strategy.
White Box approach to test case design
For designing white box test cases, testers should have a knowledge of internal logic structure of the application. The main purpose of this strategy is to determine all the logics are implemented properly. Sources such as High level design, Control flow graph and Cyclomatic complexity are used to determine test scenarios of application. Statement coverage, Decision coverage and Condition coverage are testing techniques of white box testing strategy.

Hope to cover all the testing techniques individually and See you soon with another Strategies and methods for test case design tutorial........
Thanks,
Dananji Withana

Comments

Post a Comment

Popular posts from this blog

Java basic for Selenium - Selenium Tutorial II

Today we are talking about Array. The software tester should have some basic knowledge about java when writing selenium scripts for the validations. Array is a data structure where stored in elements in same data type. The declaration and initialization an array as follows. int[]  Array_a;   or  int  Array_a[]; - This is an integer array. int[10] = Array_num;  - This is an integer array which stores 10 elements. Array_num[0] = 10;    - Assign value 10 to 0 th element of array. (Index [0]) int[]   Array_num = { 1, 2, 3, 4, 5 };  Finding maximum value of an array Finding minimum value of an array Finding average value of an array Find the key of an array Reverse an array The time complexity of this algorithm is   O(n/2)   which is O(N) because we are iterating over array till midpoint only. The initial iteration is happening as follows The...
1 comment
Read more

Strategies and methods for test case design I - Requirement traceability matrix

Requirement traceability matrix Today we are talking how to design requirement traceability matrix for Amazon web page. This is the URL for Amazon  https://www.amazon.com The process for designing requirement traceability matrix is as follows. Identifying business requirement Identifying functional requirement Identifying test scenarios Identifying test cases for each scenarios Finding validation tables for related test cases Identifying business requirement Business requirements are performed for meeting organizational objectives and finding solutions. Business requirement specification is designed by business analyst. The main objective of this document is to find out business solutions for the identified problems. It is covered customer needs and expectation. Use cases are designed after being gathered and validated business requirements. Identifying functional requirement Functional requirement specification is designed as a formal statement of application’s funct...
1 comment
Read more