US 6,725,399 B1Grant
Requirements based software testing method
Issue Date:2004-04-20
•9 Claims
•19 Drawing Sheets
Abstract
A method for testing computer software is described. The method is intended for operation on software which may or may not have been previously subjected to unit and integration tests, to determine if it will meet the specific requirements of an end user. The method is applicable to internally developed, contractor developed, or vendor supplied software. The method includes application in six key process areas. The six key process areas are development of a test plan, development of test cases to support the plan, development of an environment to simulate the technical environment in which the program will operate, test execution in which the tests are executed in a technical environment, compiling and analyzing the results and finally reporting the results in a form whereby the end user can determine both the feasibility of the software system for the specific requirements and any areas where additional testing or modifications are necessary.
Metadata
Assignee
- Compuware Corporation
Inventor
- John Bowman
Application Information
Application Number:US 09/353,872
Filing Date:1999-07-15
Priority Date:1999-07-15
Art Unit:7
Classifications
IPC:
H02H 305
Field of Search:
714 38717124
Patent Drawings (19 sheets)
Description
BACKGROUND OF THE INVENTION
[0002] 1. Field of the Invention
[0003] This invention relates to a method of testing computer software and in particular to a non invasive method for evaluating the effectiveness of computer software to perform the functions desired by the business user. The testing method of this invention is particularly suited for determining the level of effectiveness achieved by a computer program or software when tailored to a business requirement.
[0004] 2. Description of the Prior Art
[0005] Within the advent of computer software for many different domestic, commercial and industrial uses a need has grown to test that software to determine whether it will achieve its intended or desired purpose. Certain software programs are sufficiently complex that separate computer software is needed to test and evaluate whether a special purpose program will perform satisfactorily under the conditions present in a specific user situation.
[0006] For example, in U.S. Pat. No. 5,651,111 there is described a procedure where the program source code is invaded to generate a complementary source code which includes external dependencies. The testing method, then, translates the source code and complementary code to produce a machine-executable program for testing the source code.
[0007] In U.S. Pat. No. 5,758,061 an automatic testing technique generates an incremental coverage report for portions of the program that have been unreached by previous testing procedures. In that patent there is described a procedure whereby a computer program is “parsed” and instrument code is inserted in appropriate parts of the program. When the program is executed, the instrument code causes coverage results to be generated and stored. The output then is used to specify the value of a current test.
[0008] These types of procedures require access to the source code. However, when computer software is purchased the seller often does not provide access to source code because such code is proprietary. Therefore the purchaser must rely on testing procedures performed by the seller.
[0009] In unit testing, test data and various inputs to simulate various conditions under which the unit of software may operate are used. Test data are developed and a corrective action may be taken in response to test results. In integration testing software units are incrementally combined until the complete software system and the resulting integrated machine-executable programs are tested. Integration testing may involve integration of data, executable code and test result. As described in U.S. Pat. No. 5,651,111, in integration testing as in unit testing a machine-executable program is executed and the run time output or results are examined as a way to verify the correct functioning of the program being tested. Therefore, the external dependency problem of unit testing also exists for integration testing. In other words, in such testing, it is necessary to duplicate business external conditions under which the software may be expected to be called upon to function.
[0010] In U.S. Pat. No. 5,600,789 a method for automated testing of computer application programs using a Graphic User Interface is described. Simulated user events such as keyboard or mouse actions are automatically inputted into the interface which is then monitored to observe changes in response to the input.
[0011] In that method, inputs to the interface that simulate user events, such as keyboard or mouse action, are provided and the changes to the interface in response to the input are observed. The simulated user input is described as appearing exactly as if the input came from the user. A test script is written in a high level programming language and contains the events to be simulated. The script is then executed and a driver is used to take specific references and perform the actual interface to Graphical User Interface objects: Logical Screen Elements are identified and are the objects used to interface with the user. The simulated user input is sent to the graphical user interface directed at a particular Logical Screen Element. Validation, then, concerns whether the Logical Screen Element has accepted the user and entered the expected state.
[0012] The test script is described as being written in a language called “T”, although any appropriate programming language could be used.
[0013] There remains a need however for a procedure for testing both new and revised computer application programs which is independent of any specific testing tool, operating system or technical platform to direct testing activity to determine the feasibility or practicality of the use of a specific program at the user level. There is a need for determining whether a program which has been cleared by the vendor through unit and integration or other testing will adequately meet the end users needs when subjected to realistic, rather than technical, conditions.
SUMMARY OF THE INVENTION
[0014] It has been discoverd that the end user requirements for a software program can be efficiently and reliably evaluated against a software program using actual production measurements and related information. The procedure of this invention, then, not only can determine how well a product has been tested by the vendor and/or creator, but rather if the product will reliably meet the user requirements in performing specific functions, and the quality of the performance. The process of this invention provides evaluation in a succession of six key process areas leading from creation of an initial test plan through a management report on the readiness of the software under test for production service.
[0015] In the first key process area a test plan is created which defines the scope of the software test, the approach to complete the test, resources required and the acceptance criteria for the test.
[0016] The second key process area is test case development where in the test cases that support the plan are created to validate software functions.
[0017] Third key process area is test environment preparation which is used to establish a controlled technical environment for the application of the test cases. The controlled environment simulates a business environment in which the application programs will operate so that results are not skewed by technical environment variables.
[0018] The fourth key process area is test execution wherein the test cases defined in the second key process area are executed in the technical environments defined in the third key process area.
[0019] The fifth key process area is results analysis wherein a review identifies the areas of the software that need to be repaired and ultimately re-tested and the collection and analysis of metrics used to measure the software system's readiness as defined in the test plan are collected.
[0020] Finally, the sixth key process area is a management reporting function, wherein the readiness of the software system as measured by the test results collected in the fifth key process area is communicated to management.
[0021] The proper combination of the above key process areas will provide the information necessary for an organization to identify and potentially eliminate defects from software before it is implemented in a production environment.
[0022] Accordingly, it is an object of this invention to produce a non-invasive procedure for software testing to determine efficiently whether the software will meet the end user's requirements.
[0023] It is another object of this invention to provide a method for testing software wherein previously designed software is evaluated against a user's specific requirements and a determination made based upon testing specific activities on a percentage pass/fail basis to determine if a software program is suitable for a specific set of requirements.
[0024] It is yet another object of this invention to provide a software testing methodology wherein specific functions to be performed can be evaluated without altering source code or rewriting the same whereby a requirement based evaluation process is used.
[0025] These and other objects will be becoming readily apparent with reference to the drawings and following description, wherein:
BRIEF DESCRIPTION OF THE DRAWINGS
[0026] FIG. 1 is a schematic representation of the software testing process of this invention;
[0027] FIG. 2 is a schematic representation of the test planning process;
[0028] FIG. 3 is a schematic view of the test case development process;
[0029] FIG. 4 is a schematic view of the test environment preparation process;
[0030] FIG. 5 is a schematic of the test execution process;
[0031] FIG. 6 is a schematic of the results analysis process; and
[0032] FIG. 7 is a schematic of the management reporting process.
[0033] FIGS. 8-20 are schematic representations of an example of a test execution schedule.
DETAILED DESCRIPTION OF THE INVENTION
[0034] Before implementing the method of this invention an assessment of the nature of the client's software testing requirements is necessary. A test process assessment, then, is an opportunity to review, evaluate, and recommend changes to the testing processes of the end user-client. In many cases the client base has not had testing processes that can be effectively automated. Test processes need to be documented and repeatable. Additionally, requirements based testing dictates that there be clearly defined business and test requirements established and the results of tests evaluated against those requirements.
[0035] The information necessary to perform a test process assessment will need to be collected from several sources and both formal and informal test processes need to be identified, documented and evaluated. A combination of the following methods will be used to extract the required information in this assessment:
[0036] Interviews with key personnel
[0037] Existing test plan reviews
[0038] Review of test execution phase
[0039] Test results review from the last test cycle
[0040] Application development process review
[0041] Technical environment review
[0042] A management report typically would be developed which contains descriptions and recommendations for improvement. This report will be substantiated by a complete, detailed, set of working papers. The report should include but is not limited to the following:
[0043] A complete description of the current testing process
[0044] An identification of problem areas in the testing processes currently employed.
[0045] Recommendation for test process improvement
[0046] The method of testing of the present invention is composed of six key process areas which together function to provide the end process analysis on a requirements basis wherein the end user's needs are supported by an independent vendor software program or by software developed or tested by the customer or a contractor. When such a program is developed by an independent software vendor it may have been subjected to unit and integration testing by the vendor before implementation of the requirements based evaluation of the method of this invention to determine feasibility of the implementation of the vendor's program to the end user's need.
[0047] The need of this invention is initiated by a first key process area which deals with test planning. The test planning directs the creation of the software plan that represents the foundation of the software testing activities of this invention. This plan defines the scope of the software test, the approach to complete the test, resources required for completing tests and acceptance criteria for the software test. The test planning process is shown schematically in FIG. 2. The test planning process contains steps that utilize generally accepted quality assurance practices and requires the resultant test plan adequately support the reasons that caused the development of the software system in the first place.
[0048] The second key process area, as shown in FIG. 3, represents test case development. In this area, test cases are created which support the test plan that was established by the first key process area. The test case contains the test procedures and test data to complete the test procedure. Additionally, test cases are designed to validate the software functions that that are in the software. The test cases are shaped by the test approaches defined in the test plan. The test case development process is shown schematically in FIG. 3.
[0049] The third key process area, involves test environment preparation. In this key process area a controlled technical environment for the application of the test cases is established. A controlled test environment is required to simulate the production technical environment in which the application programs will operate. The basic principle of most testing is to execute the tests in a defined, controlled environment so that the results reflect the behavior of the tested item and are not skewed by technical environment variables. The test environment preparation process is shown in FIG. 4.
[0050] The fourth key process area is test execution. In this area the application of the test cases defined in key process area 2 in the technical environment defined in key process area 3 is applied. Correct test case execution dependencies must be established and used to control the flow of the tests as they are executed. Additionally, criteria that could suspend testing activity are constantly reviewed. The results of the tests are logged for review at a later time. The test execution process is shown schematically in FIG. 5.
[0051] The fifth key process area is test results analysis, wherein test results logged in key process area 4 are reviewed. The review identifies the area of the software and/or tests that need to be repaired and ultimately re-executed. Additionally, the metrics that are used to measure the software system's readiness as defined by the test plan created in key process area 1 are collected. The test results analysis process is shown schematically in FIG. 6.
[0052] Finally, the sixth key process area is management reporting, wherein the readiness of the software system is measured by the test results is communicated to the client-end user. This communication provides information regarding the operation and operability of the software, thus estimating its effectiveness when in production service. This management reporting process is shown schematically in FIG. 7.
[0053] The proper combination of these key process areas provides the information necessary to identify and potentially eliminate defects in software before it is implemented in a production environment. The activities that support this become measurable and therefore become a baseline on which subsequent processes may be improved.
[0054] In order to illustrate the method of this invention the following is an example dealing with a fictitious company, ABC Hardware, Inc. and its equally fictitious payroll software product. Each of the six key process areas identified above are implemented relative to the software testing process of this invention.
EXAMPLE 1
Test Plan for Payroll
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
TEST PLAN FOR PAYROLL PROJECT
[0055] I. Test Plan Identifier
[0056] This is a comprehensive test plan for the Payroll project
[0057] II. Introduction
[0058] A. Application Description
[0059] The payroll Project (“project”) has been created to establish a Payroll Processing system (“application”) that will support the growth plans of the Company. In the initial release, the application will process the entire Payroll processing for the company. This includes the following:
[0060] Definition and maintenance of employee information
[0061] Calculation of payroll values
[0062] Disbursement of payroll
[0063] Reporting on payroll processing
[0064] Graphical user Interface operation
[0065] Performance validation
[0066] Functionality to support additional Human Resources(HR) and Payroll processes will be added during subsequent releases of the application.
[0067] An independent software vendor (ISV), Payroll Systems, Inc., specializing in creating customized Payroll solutions for companies in the retail industry is developing the application. ABC HR specialist working conjunction with analyst personnel from the ISV will define both the application and technical requirements for the application.
[0068] The application will operate from a Windows 95 workstation. The technical structure of the application will be determined in the Application Functional Specification document produced by the ISV.
[0069] III. Goals of the Software Test Effort
[0070] The overall goal of this test is to adequately test the new Payroll software to determine its ability to support the employee growth expected as part of the Company's Business Plan. In support of this goal, there are five specific goals that will be used.
[0071] 1. Quantify the degree to which the application supports the Business Requirements that drove its development.
[0072] 2. Provide recommendations for a release decision based on the quantified results.
[0073] 3. Provide a baseline measurement system for all software testing processes at the Company. This will be done so that a continuous process improvement program can be begun to increase the efficiency of software testing efforts at the company.
[0074] 4. Complete Software Testing Activity within project schedule parameters.
[0075] 5. Complete Software Testing Activity within project cost parameters.
[0076] IV. Test Scope
[0077] The scope of the effort is the implementation of new software and the deployment of that software to multiple sites.
[0078] Since this is a new software implementation, program fixes are not applicable.
[0079] Since this is a new software implementation, regression testing of existing functions in not applicable.
[0080] A. Business Requirements to be validated:
[0081] Validate that the Payroll system will be able to do the following:
[0082] Add new employees, both US and Non-US citizens
[0083] Update the name, insurance, salary, department, and benefits fields in the employee record
[0084] Delete both individual employee records as well as purge all employee records from the database
[0085] Display employee records in detailed and list views
[0086] Find individual employee records in the databases using an ID number or the employee name
[0087] The system should be available at all stores
[0088] B. Business Requirements not to be validated:
[0089] Since this is an initial release of the application, all business requirements will be validated.
[0090] C. Business Requirements which cannot be validated:
[0091] Year end billing report. The specifications for this report have not been defined yet.
[0092] Addition of contractors. The procedure has not been defined yet.
[0093] V. Test Approach
[0094] A. Type of Testing to Be Employed
[0095] This test plan assumes that the application will have Unit and Integration testing performed by the ISV before the application is delivered to ABC Hardware testing personnel.
[0096] The approach employed in this test plan will focus on the validation of the application and technical functions identified in the application requirements. To achieve this, the following test types will be used:
[0097] Functional Test
[0098] System Test
[0099] Performance Test
[0100] Acceptance Test
[0101] Regression Test
[0102] The Function, System, Acceptance and Regression Testing activities necessary to complete this test plan have direct and severe dependencies on the function requirement and functional design of the application. The Performance Testing activities necessary to complete this test plan have direct and server dependencies on the technical requirements and technical design of the application.
[0103] Brief descriptions of each test type are as provided for reference as follows:
[0104] Functional Test
[0105] Provides a systematic demonstration that functions tested are available as specified by the business requirements, system documentation, and user manuals. A key distinction of functional testing is that it is oriented from the application specialist's perspective. Functional (Business) testing is centered around the following items:
[0106] Valid Input—identified classes of valid input must be accepted.
[0107] Invalid Input—identified class of invalid input must be rejected.
[0108] Functions—identified classes of application outputs must be exercised.
[0109] Systems/Procedures—interfacing systems or procedures must be invoked.
[0110] Organization and preparation of function tests is focused on requirement, key functions or special test cases. All test cases are documented, include predictable results, and exist in a repetitive testing environment. In addition, systematic coverage pertaining to identified business process flows, data fields that integrate to other business systems, predefined processes and successive processes must be considered for testing. Before functional testing is complete, additional tests are identified and the effective value of current test is determined.
[0111] System Test
[0112] Systems testing is the tasting of a configuration to ensure known and predictable results. String testing is an excellent example of a type of system testing. Another example of system testing is the configuration oriented system integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links and integration points. System testing ensure that the entire integrated software system meets requirements. It consists of bringing together and exercising all elements of the product in a real world, or accurately simulated, environment.
[0113] Performance Test
[0114] Performance testing determines the runtime performance of the application and its supporting infrastructure under certain conditions. Performance testing is also used to measure several system characteristics, such as processing speed, response time, resource consumption, throughput, and efficiency. Stress testing is a subset of performance testing.
[0115] Acceptance Test
[0116] Acceptance testing is the formal testing performed before the application is implemented into the production environment. Acceptance testing is generally developed and performed by the client or application specialist and is conducted to determined whether a system satisfies its acceptance criteria by validating that requirements have been met, including the documentation and business processes. Based on the results of the Acceptance Test, the customer determines whether to accept or decline the system.
[0117] Regression Test
[0118] The regression test is a series of tests to ensure that no adverse changes are introduced to the application during maintenance changes, upgrades, or other changes. Regression testing is composed of a suite of components that are rerun when a single application component has been modified. This provides confidence that the system will function with newly implemented requirements. Regression testing is often a repeating process a testing cycle.
[0119] B. Pass/Fail Criteria
[0120] Error Discovery Rate trend for test case defects. 80% Test Case Pass on final Test Run
[0121] 0% unresolved critical software defects
[0122] 100% Business Requirement Coverage
[0123] 100% Declining Error Discovery Rate trend for software defects
[0124] Declining Error Discovery Rate trend for test case defects
[0125] Test Discrepancy Reporting Procedure
[0126] Errors that are found during testing are documented by each tester and then sent to the testing manager for review. If the test manager determines that the problem is an application defect the issue is logged into the defect tracking system.
[0127] Each discrepancy is logged into one of the following categories:
[0128] Valid
[0129] Test Case Defect
[0130] Application Context Defect
[0131] Application Defect
[0132] Each week all of the reported defect are reviewed for their completion status. A report from the meeting is then sent to all test team member through e-mail.
[0133] C. Suspension Criteria and Resumption Results
[0134] Suspension Criteria—Any test run will be suspended if the following criteria is met or exceeded.
[0135] 75% or higher test case failure rate on a given test run based on the execution of the first 50 test cases executed for that test run
[0136] 10 or more General Protection Faults (GPF's) or application failures per test run
[0137] (Application Failure is defined as the user interface refusing to accept input, or display values or failing and being canceled by the relevant Windows operating systems.)
[0138] Resumption Criteria—The suspended test run will not be re-executed until the following criteria is met or exceeded:
[0139] Closed incidents the defect tracking system indicating repair of issues that contributed to triggering suspension of the test.
[0140] D. Test Deliverables
[0141] The following items will be delivered from the test effort:
[0142] Test Plan
[0143] Test Case Inventory
[0144] Test Cases
[0145] Test Environment Schedule
[0146] Test Execution Results
[0147] Application Readiness Report
[0148] Environment Needs
[0149] Configuration:
| Application Server Requirements | |
| Operating System | Windows NT Server version 4.0 |
| RAM | 4 GB |
| System/CPU Type | Application: Compaq ProLiant 6500R |
| Disk Space for Installation | 200 MB Minimum (Additional space |
| required for report data) | |
| Additional Requirements | Network access to Payroll database |
| Payroll Version 1.0b | |
| Video | VGA or better |
| CD-ROM Drive | Required |
| Mouse | Required |
| Database Server Requirements | |
| Operating System | Windows NT Server version 4.0 |
| RAM | 8 GB |
| System/CPU Type | Application: Compaq ProLiant 7000R |
| Disk Space for Installation | 500 MB Minimum |
| Additional Requirements | Available to appropriate network resources |
| Oracle 7.0 of Sybase 11 | |
| Video | VGA or betier |
| CD-Rom Drive | Required |
| Mouse | Required |
| Workstation Requirements | |
| Operating System | Windows NT Workstation 4.0 or |
| Windows 95 | |
| RAM | 32 MB |
| System/CPU Type | Pentium or better |
| Disk Space for Installation | 5 MB Minimum (Additional space |
| required for report data) | |
| Additional Requirements | Network access to main database |
| Video | VGA or better |
| CD-ROM Drlve | Required |
| Mouse | Required |
[0150] Communications:
[0151] Data communication will take place over the existing private IP network and security will be handled using an existing online security database. No special activities are anticipated.
[0152] Data:
[0153] Controlled data (data that will yield predictable results) needs to be available for testing. The process used to obtain this data should be documented for use in future projects. A process should be developed and documented for restoring the database.
[0154] F. Roles and Responsibilities
[0155] Personnel
[0156] Vendor: Payroll Systems, Inc.
[0157] Human Resources Manager: John Eigenvalue
[0158] IS Manager: Hannah Boughman
[0159] Project Manager: I. M. Bored
[0160] IS Technician: Allan Rich
[0161] QA Lead: Martin Kenneth
[0162] Test Manager: Scottie Pippen
[0163] Business Analyst: Karen Wellworth
[0164] Testers: Jake Swift, Teri Jones, Cathy Norton, Jeff Briggs, John Smith
[0165] G. Staffing and Training Needs
[0166] Entire project team needs training on the Payroll Applicant
[0167] Business Analysts need training on the basis of Functional and Performance testing.
[0168] Tools to be Used
[0169] No automated testing tools will be used to assist with the execution of this test plan.
[0170] The Microsoft Office products will be used to assist the test team in completing this test plan
[0171] The DCS/Tracker defect tracking toll will be utilized to log/track and report on the defects identified during this project.
[0172] VI. Test Effort Schedule
| Test Step Description | Estimated Start Date | Estimated Completion Date |
|---|---|---|
| Test Planning | Mar. 1, 1999 | Mar. 5, 1999 |
| Test Case | Mar. 29, 1999 | Apr. 9, 1999 |
| Development | ||
| Test Environment | Apr. 12, 1999 | Apr. 16, 1999 |
| Preparation | ||
| Test Execution | Apr. 19, 1999 | Jul. 31, 1999 |
| Test Results Analysis | Aug. 1, 1999 | Aug. 10, 1999 |
| Management | Aug. 10, 1999 | Aug. 18, 1999 |
| Reporting | ||
[0173] VII. Risks and Contingencies
| Risk | Mitigation | Contingency |
|---|---|---|
| There is a risk that | This risk can be | Reduce the scope of |
| the appropriate | controlled by steady, | the testing effort. |
| resources will not be | consistent support | |
| available at the time | from ABC Hardware | |
| and for the amount of | management. | |
| time needed. | ||
| There is | The involvement of | 1) Delay Payroll |
| a risk that the vendor | the HR Management | Release & begin a |
| product chosen for the | and Business Analyst | search for a |
| new Payroll system | personnel on the | commercial, off the |
| will not be accepted | project will mitigate | shelf package that can |
| and not utilized. | this risk. | be customized to meet |
| ABC's needs. | ||
| 2) Delay Payroll | ||
| Release & contract with | ||
| ADP for the next | ||
| 12 month period while | ||
| final solution can be | ||
| created. | ||
| Additional risks arise | The control of this | This risk is |
| primarily in the area of | risk comes in the | ongoing and will |
| Project Control. | consistent | need to be mitigated |
| communication | throughout the project. | |
| between the Project | ||
| Manager and | ||
| Management. | ||
[0174] VIII. Approvals
| Project Role | Name | Initials | Date | |
|---|---|---|---|---|
EXAMPLE 2
Decision Tree for Payroll
| ABC Hardware, Inc. |
| “Your Neighborhood Hardware Store” |
EXAMPLE 3
Test Cases for Payroll
| Date | 31 MAR. 1999 | |
| Tester | Jake Swift | |
| Test Case ID | Add US - 1.1.1.1 | |
| Bus. Req. ID | Employee Processing | |
| System | Pentium 233 w/MMX, 128 MB RAM | |
| Function | Add Employees | |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b | |
| Environment | Windows NT 4.0 (Service Pack 4) | |
| Conditions | Name - Valid, Insurance - None, Department - Admin. | |
| Benefits - None | ||
| Date | 31 MAR. 1999 | |
| Tester | Jake Swift | |
| Test Case ID | Add US - 1.1.1.2 | |
| Bus. Req. ID | Employee Processing | |
| System | Pentium 233 w/MMX, 128 MB RAM | |
| Function | Add Employees | |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b | |
| Environment | Windows NT 4.0 (Service Pack 4) | |
| Conditions | Name - Valid, Insurance - None, Department - | |
| Finance, Benefits - None | ||
| Date | 31 MAR. 1999 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.3 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payro11 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Marketing, |
| Benefits - None | |
| Date | 31 MAR. 1999 | |
| Tester | Jake Swift | |
| Test Case ID | Add US - 1.1.1.4 | |
| Bus. Req. ID | Employee Processing | |
| System | Pentium 233 w/MMX, 128 MB RAM | |
| Function | Add Employees | |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b | |
| Environment | Windows NT 4.0 (Service Pack 4) | |
| Conditions | Name - Valid, Insurance - None, Department - QA, | |
| Benefits - None | ||
| Date | 31 MAR. 1999 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.5 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - R&D, |
| Benefits - None |
| Date | 31 MAR. 1999 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.6 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Sales, |
| Benefits - None | |
| Date | 31 MAR. 1999 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.1 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payrol1 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Sales, |
| Benefits - Basic PIan |
| Date | 31 MAR. 1999 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.8 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - Self, Department - Admin, |
| Benefits - Basic Plan |
| Date | 31 MAR. 1999 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.9 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - Self, Department - Finance, |
| Benefits - Basic Plan | |
| Date | 31 MAR. 1999 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.10 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - Self, Department - Marketing, |
| Benefits - Basic Plan | |
EXAMPLE 4
Test Environment Description for Payroll
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
[0175] Test Environment
[0176] Test Server Requirements
[0177] Quantity
[0178] Single, dedicated server
[0179] Hardware Configuration
| Model | Compaq ProLiant 6500R or equivalent | |
| Processor | Two Intel Pentium II processor, 450 MHz, | |
| 512 KB Cache | ||
| Memory | 256 MB SDRAM | |
| Operating System | Windows NT 4.0 Server | |
| Keyboard | Required - no preference | |
| Monitor | Minimum 15″ | |
| Video Card | 4 MB PCI or AGP | |
| Hard Drive | Two 4.0 GB (operating system) | |
| Floppy Drive | 1.44 MB | |
| Mouse | Required - no preference | |
| Network Card | 3COM PCI 10/100 twisted pair Ethernet | |
| CD ROM Drive | Required - no preference | |
[0180] Software
[0181] Payroll Version 1.0
[0182] Payroll GUI (front end) version 1.0b
[0183] Payroll server software (back end) version 1.0b
[0184] Database
[0185] Microsoft SQL Server 6.5
[0186] Disk Space/Storage
[0187] Database Size and Space Requirements (need to ensure that enough server space is being allocated for rollbacks, table sizing, backups, etc.)
[0188] Five 9.0 G Hard Drives
[0189] Hardware RAID compatible
[0190] Communication
[0191] 10MB Network Connection, minimum.
[0192] TCP/IP protocol
[0193] Protection
[0194] Uninterruptible Power Supply
[0195] Tape Backup
[0196] DLT 35/70 (Digital Linear Tape)
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
[0197] Test Client Workstation Requirements
[0198] Quantity
[0199] 5 Windows NT Users
[0200] 15 Windows 95 Users
| Processor | Intel Pentium II processor, 350 MHz, 512 KB Cache |
| Memory | 64 MB SDRAM |
| Operating System | Windows NT 4.0 or Windows 95 |
| Keyboard | Required - no preference |
| Monitor | Minimum 17″ |
| Video Card | 8 MB AGP |
| Hard Drive | 8.0 GB or greater |
| Floppy Drive | 1.44 MB |
| Mouse | Required - no preference |
| Network Card | 10/100 twisted pair Ethernet |
| Modem | Minimum 56k v.90 3COM USR modem for remote |
| access | |
| CD ROM Drive | Required - no preference |
| Sound Card | Required - no preference |
[0201] Software
[0202] Payroll version 1.0
[0203] Microsoft Excel 8.0 or greater
[0204] Microsoft Word 8.0 or greater
[0205] Internet Explorer 4.0
[0206] Communications
[0207] 10MB Network Connections, minimum.
[0208] TCP/IP protocol
[0209] Peripheral Requirements
[0210] Printing Device: Laser Printer
[0211] Physical Access
[0212] Servers located in a controlled-access environment.
[0213] Access limited to systems support personnel.
[0214] Naming Convention
[0215] Server(s): Unique computer name, with a test identifier, within its own domain, i.e., QPTEST
[0216] Database(s): Systems and Acceptance Test Database: STAT
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
[0217] General Environment Preparation Process
[0218] The initial STAT database will be a copy of the ‘vanilla’ payroll application.
[0219] Before testing begins, approved changes from the development database will be migrated and duplicated within the STAT database. The systems administrator may perform either a selective upgrade or a full upgrade between the development database and the STAT database. A selective upgrade incorporates only those files, tables, etc. that have changed; a full upgrade is a complete copy of the development environment to the STAT environment.
[0220] Before each test cycle, a backup of STAT is taken.
[0221] The test team then executes the test cases per the schedule for that particular test cycle.
[0222] At the end of each testing cycles, a backup of STAT is taken.
[0223] Before each test cycle, a decision is made to restore from a backup or to reload the entire database.
[0224] Environment Preparation Procedures to be defined and documented:
[0225] Performing a selective upgrade between the source (i.e., development) and the target (i.e., STAT) database.
[0226] Performing a full upgrade between the source and the target database.
[0227] Access to the test database requires the test database name, a login identification number, and a password.
[0228] Each login identification number is unique.
[0229] The password must be alphanumeric, and contain 6-10 characters.
[0230] The STAT's systems administrator is responsible for setting up an employee's initial access to the system; however, the employee is responsible for changing their password and maintaining the confidentiality of their access information.
[0231] Audit and Traceability
[0232] Log access and system performance.
[0233] Hardware Protection Requirements
[0234] Both surge protectors and uninterruptible power supplies (UPS) are installed on the servers to manage power failures, fluctuations, surges, etc.
[0235] Security protections requiring both a login to the identification code and a password are required to access the servers, login to the STAT database, and login to the associated network. The site and systems administrators are responsible for setting up the accounts with the applicable access privileges.
[0236] AntiVirus software programs are setup to run at a time that minimizes the impact to the server's performance. If a virus is identified, both an e-mail and a page are sent to the systems administrator, notifying them of the virus.
[0237] Backup Processes
[0238] Identify and Document Backup Procedures
[0239] Initiate, complete, and validate a normal backup of the STAT Database
[0240] Initiate, complete, and validate an incremental backup of the STAT Database
[0241] Security
[0242] The systems administrator and an appointed backup have the access and control privileges required to backup the database as well as to restore the database.
[0243] Backup Method(s)
[0244] The following backups will be taken throughout test execution:
[0245] Normal: A backup of the entire system, to include all selected drives, directories, and files, regardless of whether or not they have been changed.
[0246] Incremental: Backup of only the files that have been created or changed since the last Normal or incremental backup.
[0247] Media Rotation Scheme
[0248] Incremental backups will be done for every day of the workweek except the last day. On the last day, a normal backup is done. On the last of the month, a disaster recover backup is done, but these media are kept offsite. The incremental backup media is reused each week. The normal backups are not reused until after completion of the implementation.
[0249] Backup Chart
[0250] Each time a backup is completed, the person making the backup must complete the information associated with the test environment's backup chart. The data that must be input includes the date, time and the contents of each backup media, who initiated the backup, and who verified that the backup was acceptable.
[0251] Location of Backup Media
[0252] Incremental backups are normal, weekly backups are kept in a secured area, within the project's computer lab; the systems administrator and their appointed backup have access to the backups.
[0253] Backups are stored away from magnetic fields and electronic devices such as video monitors, analog telephones, etc.
[0254] Remote Backup Administration
[0255] Backup processes can only be done onsite, at the location of the applications server.
[0256] Restoration Processes
[0257] Security
[0258] The systems administrator and an appointed backup have the access and control privileges required to initiate and a validate a restoration.
[0259] Restoration Procedures
[0260] Restoring data to its original location.
[0261] Identify Date State to be Restores
[0262] Select appropriate Media containing most recent backup of the requested Data State
[0263] Restore the STAT database to the desired Data State
[0264] Validate the restored Data State
[0265] Notify Test Tam of valid Data State Restoration
[0266] Archiving Process
[0267] Security
[0268] The systems administrator and an appointed backup have the access and control privileges required to initiate and validate any test data archive.
[0269] Identify and Document Restoration Procedure
[0270] Identify and document data archiving procedures
[0271] Identify and document how archives are verified.
EXAMPLE 5
Test Execution Schedule for Payroll
See FIGS.
EXAMPLE 6
Test Results for Payroll Test Cases
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
EXAMPLE 7
Summarized Metrics from Payroll Execution
| Test | Test | Test | Test | Test | |
|---|---|---|---|---|---|
| Run | Run | Run | Run | Run | |
| Test Case ID | 1 | 2 | 3 | 4 | 5 |
| Add US - 1.1.1.7 | Fail | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.7 | Fail | Pass | Pass | Pass | Pass |
| Find Employee 1.2.2.1 | Fail | Pass | Pass | Pass | Pass |
| Find Employee 1.2.1.2 | Fail | Pass | Pass | Pass | Pass |
| Del. All Employees 1.4.2.1 | Pass | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.3 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.4 | Fail | Pass | Pass | Fail | Fail |
| Add US - 1.1.1.5 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.10 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.11 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.12 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.16 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.17 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.18 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.22 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.23 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.24 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.28 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.29 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.30 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.34 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.35 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.36 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.40 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.41 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.42 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.46 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.47 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.48 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.52 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.53 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.54 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.58 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.59 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.60 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.64 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.65 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.66 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.70 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.71 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.72 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.76 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.77 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.78 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.82 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.83 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.84 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.88 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.89 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.90 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.94 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.95 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.96 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.100 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.101 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.102 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.3 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.4 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.5 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.10 | N/A | Fail | Fail | Pass | Fail |
| Add Non-US - 1.1.2.11 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.12 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.16 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.17 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.18 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.22 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.23 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.24 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.28 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.29 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.30 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.34 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.35 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.36 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.40 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.41 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.42 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.46 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.47 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.48 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.52 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.53 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.54 | N/A | Fail | Pass | Fail | Fail |
| Add Non-US - 1.1.2.58 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.59 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.60 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.64 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.65 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.66 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.70 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.71 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.72 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.76 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.77 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.78 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.82 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.83 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.84 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.88 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.89 | N/A | Fail | Pass | Pass | Fail |
| Add Non-US - 1.1.2.90 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.94 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.95 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.96 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.100 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.101 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.102 | N/A | Pass | Pass | Pass | Pass |
| Find Employee 1.2.2.2 | N/A | Fail | Pass | Pass | Pass |
| Update US 1.3.1.1 | N/A | Fail | Pass | Pass | Fail |
| Update Non-US 1.3.2.1 | N/A | Fail | Pass | Pass | Pass |
| Add US - 1.1.1.2 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.6 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.9 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.13 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.15 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.19 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.21 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.25 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.27 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.31 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.33 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.37 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.39 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.43 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.45 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.49 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.51 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.55 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.57 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.61 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.63 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.67 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.69 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.73 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.75 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.79 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.81 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.85 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.87 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.91 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.93 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.97 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.99 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.103 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.105 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.2 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.6 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.9 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.13 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.15 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.19 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.21 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.25 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.27 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.31 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.33 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.37 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.39 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.43 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.45 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.49 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.51 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.55 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.57 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.61 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.63 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.67 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.69 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.73 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.75 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.79 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.81 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.85 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.87 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.91 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.93 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.97 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.99 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.103 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.105 | N/A | Fail | Fail | Pass | Pass |
| Update US 1.3.1.4 | N/A | Fail | Fail | Fail | Pass |
| Update Non-US 1.3.2.4 | N/A | Fail | Fail | Fail | Fail |
| Del Single US 1.4.1.1 | N/A | Pass | Pass | Fail | Pass |
| Del Single Non-US 1.4.1.2 | N/A | Pass | Pass | Fail | Fail |
| Find Employee 1.2.1.1 | N/A | Fail | Fail | Pass | Pass |
| Update US 1.3.1.2 | N/A | Pass | Pass | Pass | Pass |
| Update US 1.3.1.3 | N/A | Pass | Pass | Pass | Pass |
| Update Non-US 1.3.2.2 | N/A | Fail | Fail | Fail | Pass |
| Update Non-US 1.3.2.3 | N/A | Fail | Fail | Pass | Pass |
| Add US - 1.1.1.1 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.8 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.14 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.20 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.26 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.32 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.38 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.44 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.50 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.56 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.62 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.68 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.74 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.80 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.86 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.92 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.98 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.104 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.1 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.8 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.14 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.20 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.26 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.32 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.38 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.44 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.50 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.56 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.62 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.68 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.74 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.80 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.86 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.92 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.98 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.104 | N/A | Pass | Pass | Pass | Pass |
| Update US 1.3.1.5 | N/A | Fail | Pass | Pass | Pass |
| Update US 1.3.1.6 | N/A | Pass | Fail | Fail | Pass |
| Update Non-US 1.3.2.5 | N/A | Fail | Fail | Pass | Pass |
| Update Non-US 1.3.2.6 | N/A | Fail | Pass | Pass | Pass |
| Update US 1.3.1.7 | N/A | Fail | Fail | Pass | Fail |
| Update Non-US 1.3.2.7 | N/A | Fail | Fail | Fail | Pass |
| Test Exection Statisics | |||||
| Number of Test Cases Passed | 1 | 157 | 203 | 206 | 216 |
| Number of Test Cases Failed | 49 | 74 | 28 | 25 | 15 |
| Number of Business Reqs Covered | 1 | 1 | 1 | 1 | 1 |
| Number of Test Cases Executed | 50 | 231 | 231 | 231 | 231 |
EXAMPLE 8
Application Readiness Report for Payroll Project
APPLICATION READINESS REPORT
ABC HARDWARE—PAYROLL 1.0 PROJECT
TABLE OF CONTENTS
[0272] EXECUTIVE SUMMARY 2
[0273] TEST COVERAGE MEASUREMENT 2
[0274] ERROR DISCOVERY RATE MEASUREMENT 3
[0275] TESTING ACTIVITY MEASUREMENT 3
[0276] SUCCESS STATUS MEASUREMENT 3
[0277] SPECIFIC RISK MEASUREMENT 3
[0278] OTHER TEST MEASUREMENTS 4
[0279] PROJECT SUMMARY 4
[0280] COSTS 4
[0281] OUTSTANDING ISSUES 4
[0282] RISKS 4
[0283] CONCLUSION 4
APPLICATION READINESS REPORT
ABC HARDWARE—PAYROLL 1.0 PROJECT
[0284] Executive Summary
[0285] This report will summarize the testing activities that have taken place over the last 13 months on the Payroll Project. The basis for our go/no go recommendation can be substantiated by the data contained within this report and its supporting documents.
[0286] It is the recommendation of the test team that the Payroll application NOT be released into production at this time. We are further recommending that the release date be pushed back a minimum of two months.
[0287] The primary reason for this decision is the lack of test coverage. Only one of the six business requirements has been fully tested. Current testing is on budget and needs to continue through the remaining business requirements before we will have a full understanding as to whether or not the application is ready for production.
[0288] Test Coverage Measurement
[0289] This measurement shows how many of the business requirements that were represented in the test plan have actually been tested to this date.
[0290] There were a total of six business requirements identified. Of those six, only one has been fully tested. This represents only a 16.6% test coverage measurement. The following chart graphically shows this information:
| Tested |
[0291] One of the acceptance criteria for the test effort was 100% Business Requirement Coverage. As you can tell from the chart, only 16.6% of the business requirements were tested; therefore, an acceptance criterion was not met in this area.
APPLICATION READINESS REPORT
ABC HARDWARE—PAYROLL 1.0 PROJECT
[0292] Error Discovery Rate Measurement
[0293] The error discovery number shows how many open defects there are for the application at a given point in time. This discovery rate trend should be on a downward slope as the release of the software approaches. Our trend demonstrated that the testing was effective because the number of defects did in fact decrease each month.
[0294] The following chart graphically depicts the number of open defects over the life of the Payroll project.
[0295] Testing Activity Measurement
[0296] There were a total of 231 test cases for this effort. The test team was able to successfully execute all 231 test cases. Therefore, our total activity was 100%.
[0297] This number represents an improvement over the last test effort where we were only able to complete 78% of the test cases.
[0298] Success Status Measurement
[0299] Out of the 231 test cases, 216 were successful. That represents a 93.5% success ration. Therefore, we can be certain that the results we analyze for Employee Processing are comprehensive enough to make an accurate business decision regarding the readiness of that module.
[0300] Specific Risk Management
[0301] The following chart will show what specific areas of the application will be at risk if the software is released without any further development or testing.
APPLICATION READINESS REPORT
ABC HARDWARE—PAYROLL 1.0 PROJECT
| Open Defects |
[0302] As the chart shows, there are no open defects for any business requirement except for Employee Processing. But, this is because the test team has not begun to test the other areas of the application yet. Therefore, there is a huge risk in these areas of the Payroll application.
[0303] Other Test Measurements
[0304] No other test measurements are being utilized at this time.
[0305] Project Summary
[0306] Costs
[0307] Testing costs to date total $102,000 of the budgeted $240,000. The remaining $138,000 will be used for testing the remainder of the business requirements.
[0308] Outstanding Issues
[0309] Business requirements 2, 3, 4, 5, and 6 still need to be tested.
[0310] Risks
[0311] There is a major risk in releasing the Payroll application in its current state. The risk involves the unknowns associated with not having tested over 83% of the application in this effort. The test team cannot reliably predict the problems we could face in the following business areas: payroll calcuation, payroll disbursement, payroll reporting, the applications graphical user interface, and system performance.
[0312] Conclusion
[0313] Overall, this test effort has been a very positive experience. For the first time in our company's history we have an objective way of determining if an application is ready to be released into production. We have also put measures in place to better control future testing projects and their associated costs.
[0314] All of the hard work and effort has demonstrated, unanimously, that the Payroll application is not ready to be released into production.
[0315] The main reason for this recommendation is the tact that only 16.6% of the application has been tested to this date. Our further recommendation is to push the release back a minimum of two months. This will allow enough time to finish the development work that is necessary and to thoroughly test the remaining modules of the application.
EXAMPLE 1
Test Plan for Payroll
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
TEST PLAN FOR THE PAYROLL PROJECT
[0316] I. Test Plan Identifier
[0317] This is a comprehensive test plan for the Payroll project.
[0318] II. Introduction
[0319] A. Application Description
[0320] The Payroll Project (“project”) has been created to establish a Payroll Processing system (“application”) that will support the growth plans of the Company. In the initial release, the application will process the entire Payroll processing for the company. This includes the following:
[0321] Definition and maintenance of employee information.
[0322] Calculation of payroll values.
[0323] Disbursement of payroll.
[0324] Reporting on payroll processing.
[0325] Graphical User Interface operation.
[0326] Performance validation.
[0327] Functionality to support additional Human Resources and Payroll processes will be added during subsequent releases of the application.
[0328] An independent software vendor (ISV), Payroll System, Inc., specializing in creating customized Payroll solutions for companies in the retail industry is developing the application. ABC HR specialists working in conjunction with analyst personnel from the ISV will define the both the Application and Technical requirements for the application.
[0329] The application will be operate from a Windows 95 workstation. The technical structure of the application will be determined in the Application Functional Specification document produced by the ISV.
[0330] III. Goals of the Software Test Effort
[0331] This overall goal of this test effort is to adequately test the new Payroll software to determine its ability to support the employee growth expected as part of the Company's Business Plan. In support of this goal, there are five (5) specific goals that will be used.
[0332] 1. Quantify the degree to which the application supports the Business Requirements that drove its development.
[0333] 2. Provide recommendations for a release decision based on the quantified results.
[0334] 3. Provide a baseline measurement system for all software testing processes at the Company. This will be done so that a continuous process improvement program can begin to increase the efficiency of software testing efforts at the company.
[0335] 4. Complete Software Testing Activity on within project schedule parameters.
[0336] 5. Complete Software Testing Activity within project cost parameters.
[0337] IV. Test Scope
[0338] The scope of the effort is the implementation of new software and the deployment of that software to multiple sites.
[0339] Since this is a new software implementation, program fixes are not applicable. Since this is a new software implementation, regression testing of existing functions is not applicable.
[0340] A. Business Requirements to be validated:
[0341] Validate that the Payroll system will be able to do the following:
[0342] Add new employees, both US and Non-US citizens
[0343] Update the Name, Insurance, Salary, Department, and Benefits fields in the employee record
[0344] Delete both individual employee records as well as purge all employee records from the database.
[0345] Display employee records in detailed and list views.
[0346] Find individual employee records in the database using an ID number or the employee name.
[0347] The system should be available at all stores.
[0348] B. Business Requirements not to be validated:
[0349] Since this is an initial release of the application, all Business Requirements will be validated.
[0350] C. Business Requirements which cannot be validated:
[0351] Year end billing report. This specifications for this report have not been defined yet.
[0352] Addition of contractors. This procedure has not been defined yet.
[0353] V. Test Approach
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
[0354] Test Environment
[0355] Test Server Requirements
[0356] Quantity
[0357] Single, dedicated server
[0358] Hardware Configuration
| Model | Compaq ProLiant 6500R or equivalent |
| Processor | Two Intel Pentium II processor, 450 MHz, |
| 512 KB Cache | |
| Memory | 256 MB SDRAM |
| Operating System | Windows NT 4.0 Server |
| Keyboard | Required - no preference |
| Monitor | Minimum 15″ |
| Video Card | 4 MB PCI or AGP |
| Hard Drive | Two 4.0 GB (operating system) |
| Floppy Drive | 1.44 MB |
| Mouse | Required - no preference |
| Network Card | 3COM PCI 10/100 twisted pair Ethernet |
| CD ROM Drive | Required - no preference |
[0359] Software
[0360] Payroll Version 1.0
[0361] Payroll GUI (front end) version 1.0 b
[0362] Payroll server software (back end) version 1.0 b
[0363] Database
[0364] Microsoft SQLServer 6.5
[0365] Disk Space/Storage
[0366] Database Size and Space Requirements (need to ensure that enough server space is being allocated for rollbacks, table sizing, backups, etc.)
[0367] Five 9.0 G Hard Drives
EXAMPLE 2
Test Cases for Payroll
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.1 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Admin, |
| Benefits - None | |
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.2 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Finance, |
| Benefits - None | |
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.3 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Marketing, |
| Benefits - None | |
| Date | 31 MAR 99 | |
| Tester | Jake Swift | |
| Test Case ID | Add US - 1.1.1.4 | |
| Bus. Req. ID | Employee Processing | |
| System | Pentium 233 w/MMX, 128 MB RAM | |
| Function | Add Employees | |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b | |
| Environment | Windows NT 4.0 (Service Pack 4) | |
| Conditions | Name - Valid, Insurance - None, Department - QA, | |
| Benefits - None | ||
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.5 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b. Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - R&D, |
| Benefits - None | |
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.6 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Sales, |
| Benefits - None | |
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.7 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - None, Department - Sales, |
| Benefits - Basic Plan | |
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.8 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - Self, Department - Admin, |
| Benefits - Basic Plan | |
| Date | 31 MAR 99 |
| Tester | Jake Swift |
| Test Case ID | Add US - 1.1.1.9 |
| Bus. Req. ID | Employee Processing |
| System | Pentium 233 w/MMX, 128 MB RAM |
| Function | Add Employees |
| Version | Payroll 1.0, Payroll GUI 1.0b, Payroll Server 1.0b |
| Environment | Windows NT 4.0 (Service Pack 4) |
| Conditions | Name - Valid, Insurance - Self, Department - Finance, |
| Benefits - Basic Plan | |
EXAMPLE 3
Test Environment Description for Payroll
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
[0368] Test Environment
[0369] Test Server Requirements
[0370] Quantity
[0371] Single, dedicated server
[0372] Hardware Configuration
| Model | Compaq ProLiant 6500R or equivalent |
| Processor | Two Intel Pentium II processor, 450 MHz, |
| 512 KB Cache | |
| Memory | 256 MB SDRAM |
| Operating System | Windows NT 4.0 Server |
| Keyboard | Required - no preference |
| Monitor | Minimum 15″ |
| Video Card | 4 MB PCI or AGP |
| Hard Drive | Two 4.0 GB (operating system) |
| Floppy Drive | 1.44 MB |
| Mouse | Required - no preference |
| Network Card | 3COM PCI 10/100 twisted pair Ethernet |
| CD ROM Drive | Required - no preference |
[0373] Software
[0374] Payroll Version 1.0
[0375] Payroll GUI (front end) version 1.0 b
[0376] Payroll server software (back end) version 1.0 b
[0377] Database
[0378] Microsoft SQLServer 6.5
[0379] Disk Space/Storage
[0380] Database Size and Space Requirements (need to ensure that enough server space is being allocated for rollbacks, table sizing, backups, etc.)
[0381] Five 9.0 G Hard Drives
[0382] Hardware RAID compatible
[0383] Communications
[0384] 10 MB Network Connection, minimum.
[0385] TCP/IP protocol
[0386] Protection
[0387] Uninterruptible Power Supply
[0388] Tape Backup
[0389] DLT 35/70 (Digital Linear Tape)
[0390] Test Client Workstation Requirements
[0391] Quantity
[0392] 5 Windows NT Users
[0393] 15 Windows 95 Users
| Processor | Intel Pentium II processor, 350 MHz, 512 KB Cache |
| Memory | 64 MB SDRAM |
| Operating System | Windows NT 4.0 or Windows 95 |
| Keyboard | Required - no preference |
| Monitor | Minimum 17″ |
| Video Card | 8 MB AGP |
| Hard Drive | 8.0 GB or greater |
| Floppy Drive | 1.44 MB |
| Mouse | Required - no preference |
| Network Card | 10/100 twisted pair Ethernet |
| Modem | Minimum 56k v.90 3COM USR modem for remote |
| access | |
| CD ROM Drive | Required - no preference |
| Sound Card | Required - no preference |
[0394] Software
[0395] Payroll version 1.0
[0396] Microsoft Excel 8.0 or greater
EXAMPLE 4
Test Environment Backup and Restore Procedures
[0397] Microsoft Word 8.0 or greater
[0398] Internet Explorer 4.0
[0399] Communications
[0400] 10 MB Network Connection, minimum.
[0401] TCP/IP protocol
[0402] Peripheral Requirements
[0403] Printing Device: Laser Printer
[0404] Physical Access
[0405] Servers located in a controlled-access environment.
[0406] Access limited to systems support personnel.
[0407] Naming Convention
[0408] Server(s): Unique computer name, with a test identifier, within its own domain, i.e.,
[0409] QPTEST
[0410] Database(s): Systems and Acceptance Test Database: STAT
ABC HARDWARE, INC.
“YOUR NEIGHBORHOOD HARDWARE STORE”
[0411] General Environment Preparation Process
[0412] The initial STAT database will be a copy of the ‘vanilla’ payroll application.
[0413] Before testing begins, approved changes from the development database will be migrated and duplicated within the STAT database. The systems administrator may perform either a selective upgrade or a full upgrade between the development database and the STAT database. A selective upgrade incorporates only those files, tables, etc. that have changed; a full upgrade is a complete copy of the development environment to the STAT environment.
[0414] Before each test cycle, a backup of STAT is taken.
[0415] The test team then executes the test cases per the schedule for that particular test cycle.
[0416] At the end of each testing cycle, a backup of STAT is taken.
[0417] Before each test cycle, a decision is made to restore from a backup or to reload the entire database.
[0418] Environment Preparation Procedures to be defined and documented:
[0419] Performing a selective upgrade between the source (i.e., development) and the target (i.e., STAT) database.
[0420] Performing a full upgrade between the source and the target database.
[0421] Security Requirements
[0422] Access and Privileges
[0423] Access to the test database name, a login identification number, and a password.
[0424] Each login identification number is unique.
[0425] The password must be alphanumeric, and contain 6-10 characters.
[0426] The STAT's systems administrator is responsible for setting up an employee's initial access to the system; however, the employee is responsible for changing their password and maintaining the confidentiality of their access information.
[0427] Audit and Traceability
[0428] Log access and system performance.
[0429] Hardware Protection Requirements
[0430] Both surge protectors and uninterruptible power supplies (UPS) are installed on the servers to manage power failures, fluctuations, surges, etc.
[0431] Security protection requiring both a login identification code and a password are required to access the servers, login to the STAT database, and login to the associated network. The site and systems administrators are responsible for setting up the accounts with the applicable access privileges
[0432] AntiVirus software programs are setup to run at a time that minimizes the impact to the server's performance. If a virus is identified, both an e-mail and a page are sent to the systems administrator, notifying them of the virus.
[0433] Backup Process
[0434] Identify and Document Backup Procedures
[0435] Initiate, complete, and validate a normal backup of the STAT Database
[0436] Initiate, complete, and validate an incremental backup of the STAT Database
[0437] Security
[0438] The systems administrator and an appointed backup have the access and control privileges required to backup the database as well as to restore the database.
[0439] Backup Method(s)
[0440] The following backups will be taken throughout test execution:
[0441] Normal: A backup of the entire system, to include all selected drives, directories, and files, regardless of whether or not they have been changed.
[0442] Incremental: Backup of only the files that have been created or changed since the last Normal or Incremental backup.
[0443] Media Rotation Scheme
[0444] Incremental backups will be done for every day of the workweek except the last day. On the last day, a normal backup is done. On the last day of the month, a disaster recover backup is done, but these media are kept offsite. The incremental backup media is reused each week. The normal backups are not reused until after completion of the implementation.
[0445] Backup Chart
[0446] Each time a backup is completed, the person making the backup must complete the information associated with the test environment's backup chart. The data that must be input includes the date, time and the contents of each backup media, who initiated the backup, and who verified that the backup was acceptable.
[0447] Location of Backup Media
[0448] Incremental backups and normal, weekly backups are kept in a secured area, within the project's computer lab; the systems administrator and their appointed backup have access to the backups.
[0449] Backups are stored away from magnetic fields and electronic devices such a video monitors, analog telephone, etc.
[0450] Remote Backup Administrator
[0451] Backup processes can only be done onsite, at the location at the application's server.
[0452] Restoration Processes
[0453] Security
[0454] The systems administrator and an appointment backup have the access and control privileges required to initiate and validate a restoration.
[0455] Restoration Procedures
[0456] Restoring data to its original location
[0457] Identify Data State to be Restored
[0458] Select appropriate Media containing most recent backup of the requested Data State
[0459] Restore the STAT database to the desired Data State
[0460] Validate the restored Date State
[0461] Notify Test Team of valid Date State Restoration
[0462] Archiving Processes
[0463] Security
[0464] The systems administrator and an appointed backup have the access and control privileges required to initiate and validate any test data archive.
[0465] Identify and Document Restoration Procedures
[0466] Identify and document data archiving procedures.
[0467] Identify and document how archives are verified.
EXAMPLE 5
Test Execution Schedule for Payroll
See FIGS.
EXAMPLE 6
Test Results for Payroll Test Cases
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | Execution Date | Test Run # |
| 31 MAR. 1999 | 08 JUN. 1999 | 5 |
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
| Date | 31 MAR 99 | Execution | 08 JUN 99 | Test Run # | 5 |
| Date | |||||
EXAMPLE 7
Summarized Metrics from Payroll Execution
| Test | Test | Test | Test | Test | |
|---|---|---|---|---|---|
| Run | Run | Run | Run | Run | |
| Test Case ID | 1 | 2 | 3 | 4 | 5 |
| Add US - 1.1.1.7 | Fail | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.7 | Fail | Pass | Pass | Pass | Pass |
| Find Employee 1.2.2.1 | Fail | Pass | Pass | Pass | Pass |
| Find Employee 1.2.1.2 | Fail | Pass | Pass | Pass | Pass |
| Del. All Employees 1.4.2.1 | Pass | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.3 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.4 | Fail | Pass | Pass | Fail | Fail |
| Add US - 1.1.1.5 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.10 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.11 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.12 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.16 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.17 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.18 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.22 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.23 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.24 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.28 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.29 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.30 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.34 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.35 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.36 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.40 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.41 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.42 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.46 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.47 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.48 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.52 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.53 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.54 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.58 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.59 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.60 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.64 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.65 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.66 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.70 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.71 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.72 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.76 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.77 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.78 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.82 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.83 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.84 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.88 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.89 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.90 | Fail | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.94 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.95 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.96 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.100 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.101 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.102 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.3 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.4 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.5 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.10 | N/A | Fail | Fail | Pass | Fail |
| Add Non-US - 1.1.2.11 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.12 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.16 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.17 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.18 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.22 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.23 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.24 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.28 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.29 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.30 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.34 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.35 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.36 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.40 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.41 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.42 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.46 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.47 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.48 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.52 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.53 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.54 | N/A | Fail | Pass | Fail | Fail |
| Add Non-US - 1.1.2.58 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.59 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.60 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.64 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.65 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.66 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.70 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.71 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.72 | N/A | Fail | Pass | Fail | Pass |
| Add Non-US - 1.1.2.76 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.77 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.78 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.82 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.83 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.84 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.88 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.89 | N/A | Fail | Pass | Pass | Fail |
| Add Non-US - 1.1.2.90 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.94 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.95 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.96 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.100 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.101 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.102 | N/A | Pass | Pass | Pass | Pass |
| Find Employee 1.2.2.2 | N/A | Fail | Pass | Pass | Pass |
| Update US 1.3.1.1 | N/A | Fail | Pass | Pass | Fail |
| Update Non-US 1.3.2.1 | N/A | Fail | Pass | Pass | Pass |
| Add US - 1.1.1.2 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.6 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.9 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.13 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.15 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.19 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.21 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.25 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.27 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.31 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.33 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.37 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.39 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.43 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.45 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.49 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.51 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.55 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.57 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.61 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.63 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.67 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.69 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.73 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.75 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.79 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.81 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.85 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.87 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.91 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.93 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.97 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.99 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.103 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.105 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.2 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.6 | N/A | Fail | Fail | Fail | Fail |
| Add Non-US - 1.1.2.9 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.13 | N/A | Fail | Fail | Fail | Pass |
| Add Non-US - 1.1.2.15 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.19 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.21 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.25 | N/A | Fail | Fail | Pass | Pass |
| Add Non-US - 1.1.2.27 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.31 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.33 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.37 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.39 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.43 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.45 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.49 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.51 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.55 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.57 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.61 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.63 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.67 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.69 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.73 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.75 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.79 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.81 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.85 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.87 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.91 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.93 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.97 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.99 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.103 | N/A | Fail | Pass | Pass | Pass |
| Add Non-US - 1.1.2.105 | N/A | Fail | Fail | Pass | Pass |
| Update US 1.3.1.4 | N/A | Fail | Fail | Fail | Pass |
| Update Non-US 1.3.2.4 | N/A | Fail | Fail | Fail | Fail |
| Del Single US 1.4.1.1 | N/A | Pass | Pass | Fail | Pass |
| Del Single Non-US 1.4.1.2 | N/A | Pass | Pass | Fail | Fail |
| Find Employee 1.2.1.1 | N/A | Fail | Fail | Pass | Pass |
| Update US 1.3.1.2 | N/A | Pass | Pass | Pass | Pass |
| Update US 1.3.1.3 | N/A | Pass | Pass | Pass | Pass |
| Update Non-US 1.3.2.2 | N/A | Fail | Fail | Fail | Pass |
| Update Non-US 1.3.2.3 | N/A | Fail | Fail | Pass | Pass |
| Add US - 1.1.1.1 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.8 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.14 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.20 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.26 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.32 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.38 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.44 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.50 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.56 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.62 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.68 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.74 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.80 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.86 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.92 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.98 | N/A | Pass | Pass | Pass | Pass |
| Add US - 1.1.1.104 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.1 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.8 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.14 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.20 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.26 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.32 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.38 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.44 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.50 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.56 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.62 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.68 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.74 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.80 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.86 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.92 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.98 | N/A | Pass | Pass | Pass | Pass |
| Add Non-US - 1.1.2.104 | N/A | Pass | Pass | Pass | Pass |
| Update US 1.3.1.5 | N/A | Fail | Pass | Pass | Pass |
| Update US 1.3.1.6 | N/A | Pass | Fail | Fail | Pass |
| Update Non-US 1.3.2.5 | N/A | Fail | Fail | Pass | Pass |
| Update Non-US 1.3.2.6 | N/A | Fail | Pass | Pass | Pass |
| Update US 1.3.1.7 | N/A | Fail | Fail | Pass | Fail |
| Update Non-US 1.3.2.7 | N/A | Fail | Fail | Fail | Pass |
| Test Exection Statisics | |||||
| Number of Test Cases Passed | 1 | 157 | 203 | 206 | 216 |
| Number of Test Cases Failed | 49 | 74 | 28 | 25 | 15 |
| Number of Business Reqs Covered | 1 | 1 | 1 | 1 | 1 |
| Number of Test Cases Executed | 50 | 231 | 231 | 231 | 231 |
EXAMPLE 8
Application Readiness Report for Payroll Project
APPLICATION READINESS REPORT
ABC HARDWARE-PAYROLL 1.0 PROJECT
TABLE OF CONTENTS
[0468] EXECUTIVE SUMMARY. . . . . . . . 2
[0469] TEST COVERAGE MEASUREMENT. . . . 2
[0470] ERROR DISCOVERY RATE MEASUREMENT.3
[0471] TESTING ACTIVITY MEASUREMENT. . .3
[0472] SUCCESS STATUS MEASUREMENT. . . .3
[0473] SPECIFIC RISK MEASUREMENT. . . . 3
[0474] OTHER TEST MEASUREMENTS. . . . . 4
[0475] PROJECT SUMMARY. . . . . . . . . 4
[0476] COSTS. . . . . . . . . . . . . . 4
[0477] OUTSTANDING ISSUES . . . . . . . 4
[0478] RISKS . . . . . . . . . . . . . 4
[0479] CONCLUSION . . . . . . . . . . . 5
APPLICATION READINESS REPORT
ABC HARDWARE-PAYROLL 1.0 PROJECT
[0480] Executive Summary
[0481] This report will summarize the testing activities that have taken place over the last 13 months on the Payroll Project. The basis for out go/no go recommendation can be substantiated by the data contained within this report and its supporting documents.
[0482] It is the recommendation of the test team that the Payroll application NOT be released into production at this time. We are further recommending that the release data be pushed back a minimum of two months.
[0483] The primary reason for this decision is the lack of test coverage. Only one of the six business requirements has been fully tested. Current testing is on budget and needs to continue through the remaining business requirements before we will have a full understanding as to whether or not the application is ready for production.
[0484] Test Coverage Measurement
[0485] This measurement shows how many of the business requirements that were represented in the test plan have actually been tested to this date.
[0486] There were a total of six business requirements identified. Of those six, only one has been fully tested. This represents only a 16.6% test coverage measurement. The following chart graphically shows this information:
| Tested |
[0487] One of the acceptance criteria for the test effort was 100% Business Requirement Coverage. As you can tell from the chart, only 16.6% of the business requirements were tested; therefore, an acceptance criterion was not met in this area.
APPLICATION READINESS REPORT
ABC HARDWARE-PAYROLL 1.0 PROJECT
[0488] Error Discovery Rate Management
[0489] The error discovery number shows how many open defects there are for the application at a given point in time. This discovery rate trend should be on a downward slope as the release of the software approaches. Our trend demonstrated that the testing was effective because the number of defects did in fact decrease each month.
[0490] The following chart graphically depicts the number of open defects over the life of the Payroll project.
[0491] Testing Activity Measurement
[0492] There were a total of 231 test cases for this effort. The test team was able to successfully execute all 231 test cases. Therefore, our total activity was 100%.
[0493] This number represents an improvement over the last test effort where we wre only able to complete 78% of the test cases.
[0494] Success Status Measurement
[0495] Out of the 231 test cases, 216 were successful. That represents a 93.5% success ratio. Therefore, we can be certain that the results we analyze for Employee Processing are comprehensive enough to make an accurate business decision regarding the readiness of that module.
[0496] Specific Risk Measurement
[0497] The following chart will show what specific areas of the application will be at risk if the software is released without any further development or testing.
| Open Defects |
[0498] As the chart shows, there are no open defects for any business requirement except for Employee Processing. But, this is because the test team has not begun to test the other areas of the application yet. Therefore, there is a huge risk in these areas of the Payroll application.
[0499] Other Test Measurements
[0500] No other test measurements are being utilized at this time.
[0501] Project Summary
[0502] Costs
[0503] Testing costs to date total $102,000 of the budgeted $240,000. The remaining $138,000 will be used for testing the remainder of the business requirements.
[0504] Outstanding Issues
[0505] Business requirements 2, 3, 4, 5 and 6 still need to be tested.
[0506] Risks
[0507] There is major risk in releasing the Payroll application in this current state. The risk involves the unknowns associated with not having tested over 83% of the application in this effort. The test team cannot reliably predict the problems we could face in the following business areas: payroll calculation, payroll disbursement, payroll reporting, the applications graphical user interface, and system performance.
[0508] Conclusion
[0509] Overall, this test effort has been a very positive experience. For the first time in our company's history we have an objective way of determining if an application is ready to be released into production. We have also put measures in place to better control future testing projects and their associated costs.
[0510] All of the hard work and effort has demonstrated, unanimously, that the Payroll application is not ready to be released in production.
[0511] The main reason for his recommendation is the fact that only 16.6% of the application has been tested to this date. Our further recommendation is to push the release back a minimum of two months. This will allow enough time to finish the development work that is necessary and to thoroughly test the remaining modules of the application.
[0512] In summary, a method for requirements based computer software testing has been discovered in which a computer software system designed for a specific purpose can be tested on the specific requirements of an end user to determine whether it will perform within acceptable limits. Testing the software system for specific requirements in a specific environment, according to this invention, requires the application of six key process areas.
[0513] In the first key process area a test plan is created which defines the scope of the software test, the approach to complete the test, resources required and the acceptance criteria for the test.
[0514] The second key process area is test case development wherein in test cases that support the plan are created to validate software functions.
[0515] The third key process area is test environment preparation in which a controlled technical environment for the application of the test cases is constructed. The controlled environment stimulates the business environment in which the application programs will operate.
[0516] The fourth key process area, then, is test execution wherein the test cases defined in the second key process area are executed in the technical environments defined in the third key process area.
[0517] After test execution, the fifth key process area involves analysis wherein the results are compiled and the metrics used to measure the software system's readiness as defined in the test plan are collected.
[0518] Finally, the sixth key process area is a management reporting function, wherein not only the readiness of the software system as measured by the metrics is compiled, but areas which require further testing or correction are outlined and identified.
[0519] Upon completion, the process of this invention, then, should provide the end user with a complete analysis as to whether the software system is suitable for normal production runs. This invention, then, is intended to adapt a requirements based test for a computer program to determine whether the program will perform within acceptable limits under the specific conditions required by the end user.
[0520] It will be readily seen by one of ordinary skill in the art that the present invention fulfills all of the objects set forth above. After reading the foregoing specification, one of ordinary skill will be able to effect various changes, substitutions or equivalents and various other aspects of the invention as broadly disclosed herein. It is therefore intended that the protection granted hereon be limited only by the definition contained in the appended claims and equivalents thereof.
Claims
What is claimed is:
1. A requirements based method for determining the proficiency with which a computer program will perform specific functions under specific environmental conditions, the method comprising:
providing computer software containing a program to perform a specific set of predetermined functions and identifying predetermined actual environmental conditions under which those functions are to be performed;
providing a test plan defining tests to be conducted on said program to simulate said actual environmental conditions;
creating test cases to support the test plan;
preparing a test environment that provides a controlled technical environment for application of the test cases, the test environment incorporating a set of transaction test data generated based upon the actual environmental conditions, whereby test results from application of the test cases reflect expected behavior under the actual environmental conditions;
executing said test cases and recording the results;
analyzing the test results using a pass/fail criteria and error identification and evaluation to determine test case defects, application context defect and application defects, if any; and
preparing a management report based upon the analyzed test results to identify a readiness of the program for performance under the actual environmental conditions.
2. The method of claim 1 wherein the test plan includes at least one test selected from the group consisting of Function test, System test, Performance test, Acceptance test, Regression test, Unit and Integration test.
3. The method of claim 2 wherein the Function test demonstrates availability of predetermined functions under the specific conditions.
4. The method of claim 2 wherein the Systems test tests the availability of a testing configuration of functions expected under the actual environmental conditions.
5. The method of claim 2 wherein the Performance test determines runtime performance expected under the actual environmental conditions.
6. The method of claim 2 wherein the Acceptance test determines whether acceptance criteria validating requirements have been met.
7. The method of claim 2 wherein the Regression test tests whether adverse changes are introduced during Maintenance changes and upgrades.
8. The method of claim 1 wherein said program is subjected to Unit and Integration tests prior to executing said test cases and recording the results.
9. The method of claim 1 wherein the test plan includes program requirements to be validated, requirements not to be evaluated, and requirements which can not be validated.
Patent Citations (8)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5600789(A) | 1997-02-01 | Parker et al. | Examiner |
| US5651111(A) | 1997-07-01 | McKeeman et al. | Examiner |
| US5742754(A) | 1998-04-01 | Tse | Examiner |
| US5758061(A) | 1998-05-01 | Plum | Examiner |
| US5892947(A) | 1999-04-01 | DeLong et al. | Examiner |
| US5905856(A) | 1999-05-01 | Ottensooser | Examiner |
| US5949999(A) | 1999-09-01 | Song et al. | Examiner |
| US6226784(B1) | 2001-05-01 | Holmes et al. | Examiner |
Non-Patent Literature (1)
- Humphrey, Watts. Managing the Software Process. New York: Addison-Wesley Publishing Comapny, 1989. 192-204.Examiner