My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25D - AGMT AND AMEND FOR UTLILITY BILLING SOFTWARE
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2020
>
02/18/2020
>
25D - AGMT AND AMEND FOR UTLILITY BILLING SOFTWARE
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/13/2020 5:05:54 PM
Creation date
2/13/2020 4:24:52 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Public Works
Item #
25D
Date
2/18/2020
Destruction Year
2025
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
366
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Statement of Work for enQuesta v6 Upgrade <br />solution throughout all phases of testing. SpiraTest will be initially configured by S&S and <br />standard test scripts will be preloaded. Delivery of this platform will occur prior to the SpiraTest <br />Training and Functional Test Workshop. <br />7.1.62 Test script management <br />❑ Test scripts will be stored in a hierarchical folder structure making navigation easy and <br />intuitive. Each individual test script will consist of a set of steps thatrepresent individual <br />actions the user must perform to complete the test. <br />❑ The Customer will add or modify test scripts in this folder structure. <br />7.1.63 Defect Tracking <br />❑ Incidents can be categorized into bugs, enhancements, training items, configuration <br />issues, conversion issues, and limitations (out of scope). Each type has its own specific <br />workflow and business rules. Incidents can be traced back to the test case and <br />underlying functional requirement allowing for easy reporting on the "in -process" <br />quality of enQuesta during each testing phase. <br />7.1.6.4 Test Execution & Release Management <br />❑ SpiraTest has the ability to group together various test cases using a test execution <br />wizard. At each step the user will mark pass/fail and has the ability to record a <br />bug/defect. In addition, each test run and any incidents that are created will be <br />associated with the current release of enQuesta. <br />❑ Failed test scripts can be re -tested once a fix is delivered to the test enviromnent. <br />7.1.6.5 Reporting <br />❑ A customized reporting dashboard will be available to team leaders and will include <br />the ability to create fully customized queries and reports. Reports can include things <br />such as the number of test runs completed, failed vs. passed vs. not yet run, etc. <br />7.1.6.6 Assumptions <br />❑ The Upgrade SpiraTest instances (Sandbox and PROD) will be deleted one year after <br />Go-Live- <br />Functional/Integration Testing <br />7.1.7 Functional and Integration Testing will occur at the same time using the standard and newly <br />create test scripts in SpiraTest. <br />7.1.7.1 Functional testing entails testing individual enQuesta workflows, Customer - <br />specific modifications and interfaces on their own to ensure accurate functionality and results. <br />Functional testing focuses on ensuring that each process functions on its own, independent of <br />the dependencies and the context of other processes that may be run before, after or <br />concurrently. <br />7.1.72 Integmtion testing is more focused on running enQuesta processes in the context <br />and sequencing of the Customer's daily, weekly, monthly, etc., work schedule. <br />Propriety & Confidential January 27, 2020 Page 23 of 37 <br />25D-49 <br />
The URL can be used to link to this page
Your browser does not support the video tag.