Test Case Design
A Test Case is a group of activities which executed to check
and verify the functionality or the feature of any project or the software
application. We will discuss about the designing of test cases and the importance
of test cases in this section.
Test Cases example: Test Scenarios for Login
Functionality – There are multiple possible test cases in these scenarios like:
i.
Validation for the user name and password
ii.
Validation for invalid username and
password
iii.
Validation for blank username or the
password
iv.
Providing Forgot Password functionality
v.
Send notification on entered email
address for forgot password functionality and many more test cases can be
create here in this simple scenarios
Use of Test Cases: Perform testing according to test
cases. Test Cases plays very important role in testing. Following are the
reasons which are responsible to use the test cases:
i.
Help to define the Testing Scope,
other wise tester go outside the scope of requirement.
ii.
Test Cases are required to make the
testing Very Specific. Mean to confirm exactly what need to test and
how.
iii.
Test Cases save the time and
efforts of testing. Time is very important side in SDLC.
iv.
Once the Test Cases documented properly,
then for next time new tester will not take much time to complete testing.
Techniques of Testing:
As we know that to check or test all possible test cases are
not possible for any software application. We need to test and found the all
possible bugs with the help of Testing Techniques in minimum time.
i.
BVA – Boundary Value Analysis:
Defining the boundary of testing under the specified range of values.
ii.
EP – Equivalence Partition: The
range that need to divided into equal groups/parts which have same behaviors.
iii.
State Transition Technique: The
method which used when software behavior change from one state to another
state.
iv.
Error Guessing Technique: In this
testing Test engineer guess about the error while testing. This possibility or
advantage can be taken due to Experience of Test Engineer.
How to write Test Cases – Tips, Guidelines or Best
Practice:
i.
Test cases should be transparent and
simple as more as possible.
ii.
Set your mind as End User and then Create
Test cases
iii.
Don’t repeat the Test Case
iv.
Don’t think about assumptions
v.
Make sure Test Cases Covering the 100%
scope of testing
vi.
Test Cases Should be identifiable
vii.
Testing Techniques should be implement
viii.
Once test cases created then these should
be Reviewed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
test case design, example of test cases, importance of test cases, use of test cases, test case techniques, how to write test cases – tips, guidelines or best practice, boundary value analysis, equivalence partition, state transition technique, error guessing technique
No comments:
Post a Comment