Briefing To TEST CASES

FUNCTIONAL Test Cases

The main intention of a TE is to write test cases effectively and also efficiently.

Here, the actual result is written after execution of the test cases and most of the time it would be the same as the expected result. It will be different if only the test step is failed. So, actual result field can be skipped, and we can elaborate about the bug in comments field.

Also, the input field can be removed and these details can be added in description field.

Its not that the above mentioned template is a standard one, the template can vary in each company and also with each application depends on TE and Test Lead. But, for testing 1 application, all TEs should follow a standard template which is formulated.Test cases should be written in such a way that even if a new TE should/can understand and execute the same.

When entering URL host name, host name is mentioned as development team throws the s/w to testing team after say 4 months – so we are not sure of the host name.

Username and password are not mentioned as they keep changing. The user might need to change it every 15 days depending upon the application. 

When writing functional test cases -  we 1^st check for which field we write test cases and then elaborate accordingly. If say, amount transfer is the field we are writing FT, then elaborate this is not login feature. Input is required in FT, if the application is data driven, then i/p column is required else it is time consuming.

Lessons for writing Functional Test Cases

·        Before we start writing test case, come up with options and select the best option  and then only start writing test case

·        In Expected result, use ‘should be’ or ‘must be’

·      Elaborate only those steps on which we have focus. Do not elaborate on all the      steps.

·        Highlight object names

·        Do not hard code the test case. Write a generic test case

·        Organize steps properly so that it reduces lot of execution time.

INTEGRATION Test Cases

Something which is covered in FT case should not be written in IT case and something written in IT case should not be written in ST case. Always start any test case with navigation steps to help new user understand it.

Strategy to write Integration test cases,

·         Understand the product

·         Identify the possible scenarios

·         Prioritize

·         Write the test cases according to priority

When TE is writing test cases, the factors he needs to consider are,

·         If the test cases are in detail

·         Coverage, all test case values or scenarios are depicted

·         Think in execution point of view

·         Template used to write test cases must be unique

Best test case is when less number of steps are involved, coverage is more, when these test cases are thrown to anyone, they need to understand.