Writing test cases in software testing?

writing test cases in manual testingWriting test cases in software testing?
In software engineering, a test case is a set of conditions or variables under which a tester will determine if a requirement upon an application is partially or fully satisfied. It may take many test cases to determine that a requirement is fully satisfied. In order to fully test that all the requirements of an application are met, there must be at least one test case for each requirement unless a requirement has sub requirements. In that situation, each sub requirement must have at least one test case


What characterises a formal, written test case is that there is a known input and an expected output, which is worked out before the test is executed. The known input should test a precondition and the expected output should test a postcondition.





Structure of test case


Formal, written test cases consist of three main parts with subsections:





Introduction/overview contains general information about Test case.


Identifier is unique identifier of test case for further references, for example, while describing found defect.


Test case owner/creator is name of tester or test designer, who created test or is responsible for its development


Version of current Test case definition


Name of test case should be human-oriented title which allows to quickly understand test case purpose and scope.


Identifier of requirement which is covered by test case. Also here could be identifier of use case or functional specification item.


Purpose contains short description of test purpose, what functionality it checks.


Dependencies


Test case activity


Testing environment/configuration contains information about configuration of hardware or software which must be met while executing test case


Initialization describes actions, which must be performed before test case execution is started. For example, we should open some file.


Finalization describes actions to be done after test case is performed. For example if test case crashes database, tester should restore it before other test cases will be performed.


Actions step by step to be done to complete test.


Input data description


Results


Expected results contains description of what tester should see after all test steps has been completed


Actual results contains a brief description of what the tester saw after the test steps has been completed. This is often replaced with a Pass/Fail. Quite often if a test case fails, reference to the defect involved should be listed in this column.





IN BRIEF A TEST CASE IS A DOCUMENT IN WHICH WE PERFORM SOME ACTIVITY WITH THE S/W AND SEE IF THE OUTPUT OR RESULT WE ARE GETTING IS ACCORDING TO THE EXPECTED OUTPUT OR NOT.EXPECTED OUTPUT IS GOT FROM S/W REQUIRMENT AND SPECIFICATION(SRS) WHICH IS FIRST STEP IN DEVELOPMENT OF A S/W WHICH IS MADE WITH INTERACTION B/W CLIENT AND DEVELOPER.Writing test cases in software testing?
Examples for Test Cases are here:


http://www.kabinfo.net/

Report Abuse