Tuesday 20 October 2015

Test Implementation

After Test analysis and design Test engineers mainly concentrate on preparing test cases. These test case preparation is a deep thinking process and is done either by manual or automation. If we write this test cases in manual we write them in either word, .doc or excel where as in automation we take the help of quality center.

Test cases:
According IEEE standard (829), Test cases are defined as documentation that is specifying inputs in predicted results and a set of execution condition for a test “Item”  
“ A test case is defined as a set of test inputs , execution conditions and expected results which are developed in order to compare those expected results  with actual results  such as to exercise a particular path or to verify deviations with the specific requirement “

Inputs  taken for Preparing Test cases:
There are certain inputs, that testers has to concentrate on in order to prepare the Test cases effectively. They are
Business Requirement/ Functional Specifications: Until  and unless we are aware of the requirements and basic functionality of a software we can’t prepare effective test case document
Prototype: The prototype helps in Knowing what are the Items that are used to prepare the Application.
Test Scenarios: Scenarios simply summarizes the Functionality of the application and describes us what to do

Need of Test cases:
  • Test cases identify and communicate the conditions that will be implemented in tests
  • It is necessary to verify the expected results with actual results to know the completeness and correctness of the application , So test cases make it more easier to compare
  • Test cases help in finding problems in the requirement or design of an application
  • Test cases help us in determining whether we meet the Client expectations or not.

Imagine if we doesn’t write test cases what will happen. There will be no process adherence. The deliverables which we have to submit to the client would be poor. Increase in time taken for execution, We have depend on Module owner for testing and there would be no requirement coverage tracking . we can’t track that how many requirements are covered and how many are left. So test cases are at most important in order to overcome these problems.

Test case Attributes: The quality of the Test case is determined by following attributes
Accurate: The test case will test based on the description given
Economical: The test cases will have only the steps or fields needed for their purpose.
Repeatable: A test case is a controlled experiment, It should produce the same results no matter who tests it. If only the writer can test it and get the result , or if the test gets different results for different retests , it needs more work in the set or actions.
Appropriate: A test case has to be appropriate for the testers and environment they use . If the test case is theoretically sound but require skills that none of the testers understand it then that test case will sit on the shelf .
Traceable: Test case must be traceable to requirements. It may meet all the standards but if their pass or fail criteria , results reports doesn’t matter why bothers
Self Cleaning: Picks up after itself . It returns the test environment to the pre test state.

Guidelines to write Test cases:
Be careful with your working
Make steps easy and understandable to follow
Be descriptive if necessary
Have a clear set of expected results
Write your test cases so that every tester can understand it when they go through the test cases.

Test case types: Generally the testers follow two different designs  to prepare test cases effectively  
User Interface Test case design
Functional and system based Test case design
User Interface Test case design: To prepare the test cases for usability testing, testers depend upon this method. Testers  in this method, identify the interest of customer side people and user interface rules  in the market

Functional and system based Test case design: After preparation of User Interface test case design, testers concentrate on functional and system based test case design . In this method, testers are preparing  test cases in IEEE 829 standards which we are going to discuss in the next blog.

No comments:

Post a Comment