CSE 270: Software Testing

W04 Activity: End-To-End Testing

Overview

In this exercise you will create and execute end-to-end tests for the teton chamber of commerce.

This week we have discussed end-to-end testing as part of verification and validation. As a result of the testing, the requirements document has been modified to correct inaccuracies and to add missing information. A new version is available in a link below, and the changes have been highlighted for ease of use.

The development team has also reviewed our test case reports and corrected several errors. They have now has created a version 1.1 for us to test. 

This version of the site now also contains the Directory page which was missing from the version 1.0. This version should complete all the requirements listed in the requirements document.

First you will use the acceptance criteria in the Directory section of the requirements document to generate new test plans for the Directory page with accompanying test cases using the Requirements and Test Management plug in for Jira. You will also need to update any test cases with the new information found in the requirements document. You will have four test plans when complete. One each for Common, Home Page, Join Page and Directory Page with their relevant test cases included.

The result will be a traceability matrix that shows you have test case coverage for all your requirements prior to completing the end-to-end testing. You will then perform an end-to-end test on the system.

Instructions

Part 1

You must have completed the previous lab W02 Activity: Test Case Generation before beginning this activity.

Access the updated requirements document here: Teton Idaho Chamber of Commerce Web Site Requirements Document version 1.1

Using the RTM for Jira program, create test plans and test cases for the following:

Section 4: Directory Page Requirements

• Create a component in Jira for the Directory Page
  • To create a component, choose the Components item in the sidebar navigation, then click the blue Create component button as before.
  • Use Jira components rather than the new "Compass" components
• Create a folder in the Requirements area for the Directory Page using the new folder button.
  • Inside each folder create a requirement in RTM for each requirement in the requirements document for that section
  • Copy the requirement text and acceptance criteria from the requirements document to the description section of each requirement created.
  • Assign the appropriate component to each requirement as you create it.
  • When completed, there will be 2 requirements in the Directory Page folder along with the folders created earlier.
• Create test cases for each of the new acceptance criteria in the requirements
  • For each test case you create, be sure to link it to the appropriate requirement
  • In each test case include the following
    • Prerequisite steps (typically found in the given and when)
    • Execution steps including any test data
• Update test cases for each of the acceptance criteria that have changed in the requirements.
• Create a test plan for the Directory Page
  • Assign the test plan to the appropriate Jira component
  • Add each of the test cases for the given component to the test plan

• Generate a traceability matrix to demonstrate the completeness of your coverage.
  • Follow the instructions found in the page W04: Creating a Traceability Report in RTM
  • Generate a PDF document of your traceability matrix, you will submit this reports as part of the assignment.

Part 2: Test execution

Now it is your job as a tester to execute the test cases and report on the results. This week, when you encounter defects, you must make a defect report. Start now with W03 Activity: Creating a Defect Report in RTM, if you did not follow the instructions in it during Week 03 to create your defect folders.

• Refer to W03 Activity: Using RTM to Execute Tests and Report Results for specific instructions on how to execute tests and report results as required below.
• Create a test execution folder for Week 4, place all test executions created in the next step in this folder.
• Using RTM, create a new test execution for each of the four test plans you created in Part 1.
• Execute all the test cases for the Common, Home, Join and Directory test plans.
  • Execute your tests against the 1.1 version of the Teton Chamber of Commerce web site found here:
    • Teton Chamber of Commerce Site - 1.1
  • Document the results of executing the tests in the RTM execution you created indicating pass or fail for each test.
  • If a test fails, generate a defect report by following the instructions in Creating A Defect Report in RTM and include the following information:
    • Priority (use the provided field in RTM)
    • Summary of the error (bug title).
      • Include the acceptance criteria number (1.1.1) in the title.
      • Procedure steps to reproduce the error
      • Expected results / Actual Results
      • Any other relevant notes about the environment (for example, which browser was used, etc.)
    • Note: Other fields like tester's name, date and time are captured automatically by Jira when a new defect is created.

Hint: Not all of your tests should pass. I've left you at least a few mistakes to create defect reports about.

Submission:

Upload the following 3 documents to Canvas

1. Your traceability matrix from Part 1
2. PDF report of the Test Executions
   • Generate your report from the Test Execution Folder that contains your executions for this week.
   • All four test plan executions should be included in this single report.
   • Ideally there will be 29 test cases now, one for each acceptance criteria.
3. PDF printout of ONE of your defect reports
   • Go to the Defects tab and choose one of your defect reports in the side navigation.
   • In the details pane, click on the issue id to open the issue in a new window.
   • In your browser menu, choose Print... then "Save as PDF" for the print destination.
   • Submit the generated PDF file 

Useful Links:

• Return to: Week Overview | Course Home | Canvas