Why One Needs To Make Use Of Software Test Cases
Software developed by the software developers, are tested to see whether they are performing up to the mark, and to test any flaws in the software. Software Test Cases are a collection of test programs, test data, and the results obtained. A software test case is a set of one or more conditions that validates whether a requirement is fully satisfied.
The number of test cases required to test a particular condition may vary from condition to condition. Many test cases may be required to determine whether a requirement is fully met as desired.
There are many methodologies adopted to form test cases. For example, there is one methodology known as the RUP methodology, in which there are exactly two test cases associated with a single requirement. One of the cases performs negative testing on the requirement, and the other case performs the positive case on the requirement.
A written software test case should include a description of the functionality of the test, and the methodology adopted to test the requirement. In case an application is created, without the formal requirements, the test cases are the normal operations of the program. In other words, the test cases are not written. Instead all the activities and results are just reported after the test has been done. In case the application is created, with the formal requirements, the test cases are actually in written, where there is an input which is known and an expected output which is achievable before the test is executed. The input test is a pre-condition and the output tests the post-condition. A formal written software test case has three parts which are then divided into subparts. These parts are Information, Test Case Activity, and the Results. The information contains any type of information related to the test case. For example, the information may contain information related to the identifier, test case creator, name of the test case, purpose of the test, version number of the test case, etc. The test case activity part of the formally written test case includes some sub-parts that contain information related to testing configuration, initialization, finalization, actions to be carried on to complete the test, a description about the input data, etc. Result part of the test case contains information about the expected results or the actual results. Expected results are the results which the tester feels are obtainable after the test has been completed. Actual results are the results actually obtained when the test is completed. In this article we have discussed what the software test cases are, and what their structure is, and, more importantly, why they are so important.
Software Testing Tools >> Privacy Policy
| 
