Overview
On an agile team, the tester’s role goes beyond merely testing for bugs. One of the key responsibilities of the tester is to work closely with the Product Owner, ensuring that test cases evaluate the needs outlined by the user stories. Identifying ambiguity in the user stories and developing scenarios to meet the acceptance criteria helps ensure that the development team will deliver the desired product. The tests that are developed could become part of the acceptance criteria for a story, or possibly another story in the Product Backlog.
Prompt
Part I: Initial Test Cases
Develop a detailed test case for each of the three user stories that you submitted in Module Three. Be sure to use the
CS 250 Module Four Test Case Template Spreadsheet
to complete this assignment. The first sheet of the template includes a sample test case for you to use as a guide in writing your test cases.
For each case, be sure to:
A. Include a descriptive name for each test case.
B. Identify detailed steps that will need to be taken by the user to complete the action identified in the user story.
C. Indicate clear pass/fail measures for each step.
Part II: Revising Test Cases
While developing the test cases, it is typical to find that you need more information or clarification from the Product Owner. Read a sample tester’s email to the Product Owner requesting clarifications of the user stories for the SNHU Travel project:
CS 250 Module Four Tester Email PDF. (Note: The order of the user stories in the email may not match up with your order, but the content of the user stories should be fairly close).
Next, you will review the wireframe supplied by the Product Owner in response to this email. To do this, download the SampleSlideShow ZIP file to your computer. Right-click on the folder and select “Extract All…”. In the unzipped folder, find and run the Top Destinations Slide Show JAR file. You will notice that this wireframe is a newer “Slide Show” format, which means you will need to make adjustments to your initial test cases as the user’s actions will change.
You will add on to the same template to complete this assignment. For each case, be sure to:
A. Copy each of your original test cases into the “revised test case” sheets in the template. Preserve the same names that you used originally.
B. Revise the steps taken by the user to complete the action identified in the user story.
C. Indicate clear pass/fail measures for each revised step.
Guidelines for Submission
Submit your completed test case template for this assignment. Be sure that you have completed all three initial test cases and three revised cases for the user stories from your Module Three User Stories Assignment.
Tester Email
image1.tmp
Test Case Template
Test Case ID:
Example #1
Test Name:
Top Five Destination List Test Case
Test Owner:
Tester
Test Designed Date:
1-Jan-17
Method – Automation? (Yes/No)
No
Work Product:
User Story #1 – Top Five Destination List
Priority (Low/Med/High):
High
Pre-Conditions
User on main SNHU Travel Website
Test Steps
Inputs
Expected Results
1. Click link titled “Top 5 Destinations”.
Browser opens webpage with the title “Top 5 Destinations”.
2. Scroll up and down webpage to view each of the top 5 destinations.
There are 5 total listings for the top destinations.
3. Verify the destinations are in an ordered list from 1 to 5.
The order should show the top destination in spot #1 and accordingly through spot #5.
4. Verify that each destination listing has the required components.
Each listing contains a picture, a short description, and a link to the top travel-package-deal booking.
Test Case #1
ID:
Name:
Owner:
Date:
Work Product:
Priority:
Pre-Conditions
Test Steps
Inputs
Expected Results
1.
2.
3.
4.
5.
Test Case #2
ID:
Name:
Owner:
Date:
Work Product:
Priority:
Pre-Conditions
Test Steps
Inputs
Expected Results
1.
2.
3.
4.
5.
Test Case #3
ID:
Name:
Owner:
Date:
Work Product:
Priority:
Pre-Conditions
Test Steps
Inputs
Expected Results
1.
2.
3.
4.
5.
Revised Test Case #1
ID:
Name:
Owner:
Date:
Work Product:
Priority:
Pre-Conditions
Test Steps
Inputs
Expected Results
1.
2.
3.
4.
5.
Revised Test Case #2
ID:
Name:
Owner:
Date:
Work Product:
Priority:
Pre-Conditions
Test Steps
Inputs
Expected Results
1.
2.
3.
4.
5.
Revised Test Case #3
ID:
Name:
Owner:
Date:
Work Product:
Priority:
Pre-Conditions
Test Steps
Inputs
Expected Results
1.
2.
3.
4.
5.
Top Destinations Slide Show.jar
META-INF/MANIFEST.MF
Manifest-Version: 1.0
Class-Path: .
Main-Class: SlideShow
SlideShow$1.class
synchronized
class SlideShow$1
implements java.awt.event.ActionListener {
void SlideShow$1(SlideShow);
public void
actionPerformed(java.awt.event.ActionEvent);
}
SlideShow$2.class
synchronized
class SlideShow$2
implements java.awt.event.ActionListener {
void SlideShow$2(SlideShow);
public void
actionPerformed(java.awt.event.ActionEvent);
}
SlideShow$3.class
synchronized
class SlideShow$3
implements Runnable {
void SlideShow$3();
public void
run();
}
SlideShow.class
public
synchronized
class SlideShow
extends javax.swing.JFrame {
private javax.swing.JPanel
slidePane;
private javax.swing.JPanel
textPane;
private javax.swing.JPanel
buttonPane;
private java.awt.CardLayout
card;
private java.awt.CardLayout
cardText;
private javax.swing.JButton
btnPrev;
private javax.swing.JButton
btnNext;
private javax.swing.JLabel
lblSlide;
private javax.swing.JLabel
lblTextArea;
public void SlideShow()
throws java.awt.HeadlessException;
private void
initComponent();
private void
goPrevious();
private void
goNext();
private String
getResizeIcon(int);
private String
getTextDescription(int);
public
static void
main(String[]);
}
resources/TestImage1
resources/TestImage2
resources/TestImage4
resources/TestImage5
resources/Testimage3