Type of Computing Environments

Web-based, Mainframe Batch

Purpose of Testing

To validate business processes are supported by the customized application.

Type of Software

Vendor-developed, Web-based

Scope of Testing

A/P, A/R, Payroll, HR, Integration with existing systems

Critical Success Factors

Security, Correctness, Performance, Ease of Use, Interoperability

Phases of Testing

Unit, System, UAT

Audience

Internal – Accounting, Payroll, HR, new and existing employees, personnel in interfaced systems

Tradeoffs

Scope, Cost

Types of Testing

Functional, based on: Business processes, Security policies, Use cases

Development Tools and Test Tools (e.g., GUI builders, automated capture/playback, etc.)

Screen capture, test management, defect management

Business/operational concerns

Payroll processing must be correct – could be fined if in error

HR processing must be correct

Accounting processing must be correct

Performance times must be within specified limits

Risks

Application Risks - Security, Correctness, Data conversion

Project Risks – Lack of experience with application and technology, No defined requirements, No defined processes, High employee turnover

Constraints

Lack of time, lack of management support, lack of experience, lack of dedicated test environment

Assumptions

Critical need of new application, Ongoing vendor support, vendor will customize application, vendor will fix defects

Deliverables

Final test report, Defect log, Baseline of correct test results for future tests

Sample Test Strategy Worksheet

Project Phase Testing Phase Stakeholders Purpose/Why