Test and revise

Test

  • Qa
  • Ax
  • Ux
  • Dv
  • Fe
  • U
  • St
  • An
  • Pm
  • I

Testing is a critical part of software development. While usability and unit testing occurs continuously during the Design and Build stages, allowing for a continuous feedback loop, it is in this distinct Test phase that all aspects of an application receive final close scrutiny and inspection. Testers work with the core project team to review the business requirements and user stories defined throughout the development process and validate that they are met in the final product. Clients and stakeholders take a final walkthrough before providing sign-off. The main objective is to find anything not working as-intended by the project team. At the end of this phase, the application should be of shippable quality.

As issues are discovered, the core project team works to revise the design or coding as needed. In some cases, remediation may not be possible before deployment; in this case, the remaining issues are prioritized for future releases. For third-party or vended software, issue findings should be shared with implementers or the vendor, so a remediation plan can be created.

Project activities

  • Testing protocols (functional, compatibility, accessibility, performance, vulnerability, automated, integration, mobile)
  • Final user acceptance testing
  • Revision and retesting for prioritized issues
  • Prioritization and planning for deferred issues

Deliverables and outcomes

  • Client sign-off
  • Software approved for deployment
  • Issue report (typically for vended or third-party software)
  • Test reports (AppScan report, performance test results)
  • Automated test scripts
  • Logged issues/backlog

Deploy