Sample test case templete




Comments

Post a Comment

Popular posts from this blog

Dividing the Test into Two Actions

Here i explained how to divide the test into two actions. Follow the below steps: Since your test currently contains two main processes: signing-in and purchasing a flight, it makes sense to divide the test into separate actions. 1. Select the page where you want the second action to begin.  In the Keyword View, expand Action1 > Welcome: Mercury Tours. 2. Split the test into two actions . Select the first Find a Flight: Mercury page and choose Edit > Action > Split Action or click the Split Action button . The Split Action dialog box opens. 3. Enter names and descriptions for the two actions. In the Name box of the 1st action type: Sign_in. In the Description box of the 1st action, type: Enters user name and password to sign in. In the Name box of the 2nd action type: FlightOrder. In the Description box of the 2nd action, type: Chooses and purchases a flight. Click OK to close the Split Action dialog box and accept the other default selections....
Read more

Inserting Calls to Actions

First, you will insert calls to the reusable Sign_in and ReturnHome actions from ActionA into ActionB. Open a new test   . For more information, see step 1 of Recording a Test. Insert a call to the Sign_in action. Choose Insert > Call to Existing Action. The Select Action dialog box opens. Click the browse button next to the From test box. Select the ActionA test in the Open Test dialog box, and click Open. Note that only reusable actions from the ActionA test are displayed in the Select Action dialog box. Select the Sign_in action. In the Location area, select At the end of the test. Click OK. The call to Sign_in [ActionA] action is added to the end of the test as a call to an external action with the icon. Note that you cannot expand the Sign_in action call in the test flow in the Keyword View. To view the steps in the Sign_in action, select it from the Action List. The action call you inserted is read-only. To modify the action, you must open the origin...
Read more

Testing during project life cycle

Testing during project life cycle: The Tenure of the project and the number of Roll-outs forms the criterions whether the project life cycle testing should be automated or not. If the automated scipts already exists, the same may be fine tuned for the said projects/Roll-outs. For the new projects and Rollout the following testing cycle can be automated: Project-Unit testing: This can be intitally manual during the build/development cycle but subsequently can be automated.It will aid in saving time and effort if changes and new requirements are introduced during project execution cycle. At this stage, both individual and combined test scripts can be used for the SAP transactions that form unit testing cycle. If the automated scripts already exists, the owner of the automated testing scripts can provide already validated scripts for the current and future projects. Project integration Testing: Automated testing can be helpful in integration testing cycle for projects. However, t...
Read more