1. Test Case ID: 01 Bill – PASS
Test Case Title: Missingapp with issuesgetsadded Eric – PASS
Test Case Conditions: Kong – PASS
Test Date: 11/10/2015
Description: An application that wasmissingfromthe list, andit gets added mid-reporting. A couple issuesalready existed for the application in theIssuesLog.
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Issuesalready show in data See issues inrawdata Issues Exist Pass
2 App showson refresh App pops up in list afterrefresh App showed upafter 1 refresh Pass
3 Issuesmap to App Issues autopopulate withapplication The issues showed upunder the app Pass
4 Validate formatting Supports SP List Values Matches List Pass
5 Validate content Supports SP List Values Matches List Pass
Test Case ID: 02 Bill – PASS
Test Case Title: Existing Appgets assignedan issue Eric – PASS
Test Case Conditions: Data already exists Kong – PASS
Test Date: 11/10/2015
Description: An issuethat is reportingunder a particular application A is actually an issuethat pertains toanother existingapplication B. The existing“green”
application B is assignedtheissue (medium, high,or critical) thatbelongedto application A.
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Issuesalready show in data See issues Issues exist Pass
2 Appsalready show in data See apps Apps exist Pass
3 Map issuesfrom A to B Name appears intheFinalApp Listand
DSR Rules Say =Show
The final applistupdates andthe
rules column says show
The rules column is new,
compares thedeployeddate
to the createdateofthe
issue along with report logic.
Pass
4 Click Refresh Issues movefromapp Ato app B Issues movetoappB Pass
5 Validate formatting Supports Override, thenSP List Matches Override Pass
6 Validate content Supports Override, thenSP List Matches Override Pass
Test Case ID: 03 Bill – PASS
Test Case Title: Manager asksfor an issueto not report Eric – PASS
Test Case Conditions: Issue currently reporting Kong – PASS
Test Date: 11/10/2015

2. Description: An application with x number ofissues is reportingon theissues. A manager asksfora particular issueto not show up on the report. The user is not
allowedto updatethe SP list.
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 App showsin data See app App exists Pass
2 Issue showsin data See issue Issue exists Pass
3 Set the issue OVERRIDE The overrideis now=Hide Override is =to “Hide” Pass
4 Click Refresh The issuevanishes fromreport Issue goes away Pass
5 Validate formatting Supports override Matches override Pass
6 Validate content Supports override Matches override Pass
Test Case ID: 04 Bill – PASS
Test Case Title: DeployedSuccessful willnotcollect issues, even valid
issues
Eric – PASS
Test Case Conditions: Issue is createdafter app setto Deployed
Successful. The issue is open and nota pre-deployment issue
Kong – PASS
Test Date: 11/10/2015
Description: There is a rule that saysissues donotshow if closed orpre-deployment. Issues should not show upafter an application deploys. An appdeploys and
is reportedon as deployedsuccessfully without any issues. Then an open/non-pre-deployment issue is createdandassignedto the app. The appcontinuesto report
without adding issuescreatedafter thedeployment date/time (actual time,not SP List value).
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 App Deploys The app turns blueand movedto
bottom saying “DeployedSuccessfully”
The app is blueand atbottomwith no
issues
Pass
2 Issue Created The issueshows upin theraw data The issuepops upin the raw data Pass
3 Click Refresh The app does notdisplay the issue The issuemarked Hidein the rawdata Pass
4 Validate formatting Does NOTsupport theSP Listvalues,
the issues wouldnormally show
The issuedoes not show up Pass
5 Validate content Does NOTsupport theSP Listvalues,
the issues wouldnormally show
The issuedoes not show up Pass
Test Case ID: 05 Bill –
Test Case Title: Track Only appgetsaddedas rolled,additionalissue
added
Eric –
Test Case Conditions: Any issue thatgetsaddedto a RB or PRB should
show up unless user overridestheissue. Test both sides.
Kong –
Test Date: 11/12/2015

3. Description: Whathappensto thereportoncea TO itemgets added? Whatabout when theissueskeep rolling in forthat TO item?
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Add Appsto TOlist Shows up in report footer withred
color
Pass
2 Create new issue or map
issue with > Rolled Date
Issue willshow upin report for RB Pass
3 Existing Issue or < Rolled
Date getsmapped
Issue willshow upin report for PRB Pass
4 Click Refresh All issues continueto showup for app Pass
5 Validate content and
formatting
These Apps only found in theTO list as
rolled or deployed. Issues will continue
to populate for rolled back apps where
CDate>Rdate.
Pass
Test Case ID: 06 Bill –
Test Case Title: Track Only appgetsaddedas deploy,additionalissue
added
Eric –
Test Case Conditions: Any issue thatgetsaddedto a DS or DWIshould
not show up unless user overrides the issue. Test both sides.
Kong –
Test Date: 11/12/2015
Description: Whathappensto thereportoncea TO itemgets added? Whatabout when theissueskeep rolling in forthat TO item?
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Add Appsto TOlist Shows up in report footer withblue
color
Pass
2 Create new issue or map
issue with >Deploy Date
Issue willnot show up Pass
3 Existing Issue or < Deploy
Date getsmapped
Issues show upfor DWI, should not be
enteredfor DS so keep aneyeon them
Pass
4 Click Refresh Issues show upfor app butnotafter
dep date.
Pass
5 Validate content and
formatting
Hide overridefor DS issues
CDate<Ddate works. Eachissueis
correct colorand only shows for
existing DWIapps
Pass
Test Case ID: 07 Bill –

4. Test Case Title: The status reason section expandsfor both redandyellow Eric –
Test Case Conditions: Thisis post refresh click. Each cell is expectedto
have a customheight to contain allof statustext.
Kong –
Test Date: 11/12/2015
Description: We now have customheightfor rows,allowingstatustext to display andmaking it so thattheuser will nothaveto expand the cells.
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 After refresh enter status’ Type rows oftextwithout expanding
cells
Pass
2 Prep Report Click See third row Pass
3 Send Email Wait time1 min for generate Pass
4 Validate Email Each cell is perfectsize for report Pass
Test Case ID: 0 Bill –
Test Case Title: T Eric –
Test Case Conditions: A Kong –
Test Date: 11/12/2015
Description:
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
Test Case ID: 0 Bill –
Test Case Title: T Eric –
Test Case Conditions: A Kong –
Test Date: 11/12/2015
Description:
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Pass
2 Pass
3 Pass

5. 4 Pass
5 Pass
Test Case ID: 0 Bill –
Test Case Title: T Eric –
Test Case Conditions: A Kong –
Test Date: 11/12/2015
Description:
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
Test Case ID: 0 Bill –
Test Case Title: T Eric –
Test Case Conditions: A Kong –
Test Date: 11/12/2015
Description:
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
Test Case ID: 0 Bill –
Test Case Title: T Eric –
Test Case Conditions: A Kong –
Test Date: 11/12/2015

6. Description:
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass
Test Case ID: 0 Bill –
Test Case Title: T Eric –
Test Case Conditions: A Kong –
Test Date: 11/12/2015
Description:
Step Test Description Expected Result Actual Result Notes Status (Pass/Fail)
1 Pass
2 Pass
3 Pass
4 Pass
5 Pass