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 created a version 1.1 web site 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 Squash. 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.

Squash provides a traceability report that shows you have test case coverage for all your requirements prior to completing the end-to-end testing. After you verify full test coverage you will then perform an end-to-end test on the system.

Instructions

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 Squash Test Management, create requirements, test plans and test cases for the following:

Section 4: Directory Page Requirements

1. Add requirements to Squash for the Directory page.
   • Create a folder for the Directory page in the Requirements section of Squash.
   • Add each requirement in Section 4 of the Requirements document to the new folder.
2. Create test cases for each of the new acceptance criteria in the Test cases section of Squash.
   • Add a new folder named Directory to the Test cases section of Squash.
   • Create a test case for each new acceptance criteria in the Directory section of the requirements document.
   • For each test case you create, be sure to link it to the appropriate requirement
   • Add each the steps for each acceptance criteria to the test case as you did for the other pages.
3. Create a Test plan for the Directory page in the Executions section of squash.
   • Create a new test plan (campaign) for the directory page.
   • Add each of the test cases for the directory page to the test plan

Update acceptance requirements

Several of the acceptance criteria have been modified in the updated Requirements document (they are indicated in bold text)

1. Update the necessary steps in the test cases by modifying/adding steps as necessary.

Test case coverage

It is important to ensure that all requirements are covered by test cases. This can quickly be determined by a traceability matrix or in the case of our testing tool a requirements coverage report or visually using the dashboard view of the requirements.

• View test case coverage using the dashboard.
  1. Open the Requirements view in Squash using the left navigation bar.
  2. Select the Teton CoC project to see coverage for the whole project. If you wish to see coverage for a specific area, select that area.
  3. Select the dashboard view. We are mostly interested int the top left pie chart. If there is red slice (which indicates Requirements that do not have a test case associated with it.) you do not have complete test coverage. You can click on the pie slice to see a list of the requirements that are not covered.

     

• Create a test case coverage report (traceability matrix).
  1. Open the Reporting view in squash using the navigation bar.
  2. Click the plus icon then select the Add a report menu item.
  3. Choose the report.
  4. Configure the report as follows:
     • Name Traceability.
     • Leave other fields as they are.
  5. Click the Add button to create the report.
  6. Execute the report by clicking the download icon.
  7. Select the Project requirement list link.

     

     Any requirement that has a 0 int the assocait column is not covered by any test cases an indicates incomplete testing.
  8. Change the download type to pdf.
  9. Click the Download button to download your report.
  10. Save the report as yourname-traceability.pdf where yourname is your last name.

Prepare for defect tracking

This time as you test, when a defect is discovered you will create a defect report. Most organizations will use a bug tracking system to manage defect tracking. For our class you will use a simple spreadsheet to record and track software bugs.

1. Download the defect tracking spreadsheet cs270-defect-tracker.xlsx.
2. The spreadsheet has three tabs. Select the first tab Project Details.
3. Enter the current date in the date cell, and your name as the project manager.
4. The second page is where you will record any defects found.
5. This document will be submitted as part of your assignment submission.

Test execution

Now it is your job as a tester to execute the test cases and report the results.

1. If you can't remember how to conduct tests Refer to Tutorial: Test Execution for specific instructions on how to execute tests and report results as required below.
2. Create a new test iteration for each test plan in squash. Name the iteration yourname W4 where yourname is your last name.
3. Execute all the test cases for the Common, Home, Join and Directory test plans.
   Hint: Not all of your tests should pass.
   • 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 Squash, indicating pass or fail for each test.
   • If a test fails, enter the following information the defect tracker spreadsheet.
     • Defect date: The date the defect was found.
     • Status: New
     • User impact: Choose an impact you feel is appropriate.
     • Business impact: Choose an impact you feel is appropriate.
     • Subject: The test tile that failed e.g. 2.1.1 Hero image.
     • Reported By: Enter your name
     • Defect/Issue Describe: Describe the nature of the defect include specific details required to reproduce error.
     • Environment: Any relevant notes about the environment (for example, which browser was used, etc.)
4. When you are done testing, create a test results report.
   • Go to the Reporting section of squash.
   • Select the Test Results report you created in week 3.
   • Click the download icon to run the report.
   • Download the Campaign monitoring dashboard as a pdf file, name it yourname-dashboard.pdf where yourname is your last name.
   • Download the Test case list by campaign as a pdf file, name it yourname-tests.pdf where yourname is your last name.

Submission:

Upload the following documents to Canvas

1. Your completed defect tracker spreadsheet.
2. Your pdf traceability report from step 4.
3. Your pdf Campaign monitoring dashboard report from step 5.
4. Your pdf Test case list by campaign report from step 5.

Useful Links:

• Return to: Week Overview | Course Home | Canvas