Sample Timeline: Platform-as-a-Service Implementation

Business Analyst works with product owner to document system requirements

System requirements definition:

• System requirements that are captured as acceptance criteria can be used as test cases for functional testing 

Project Manager creates project plan.

Include test planning as part of the project plan:

• Meet with Release Engineering team manager to consider testing needs for the project
• Consider manual testing for this type of project

Manual test planning: Utilize system requirements. Validation by developer and BA that application and APIs are behaving as expected.

Unit function tests for APIs. Created by developer. Consult with Release Engineering as needed. 

API Performance testing: Validate API performance in isolation from application.

Continuous Integration: Utilize Travis to execute unit tests automatically for each application build.

One application feature complete

API Unit tests: Release Engineering validates API unit tests

Systems Integration: Validate integration of application with APIs and other backend services 

Application available in Test environment

Performance Testing:

• BA or product owner determines test cases and expected response times
• Test environment scaled similarly to production in order to deliver valid test results
• Load testing: Validate that average response times are consistent with product owner expectations.

Systems Integration Testing (SIT):

• Validate integration of application unit tests, API unit tests and other backend services

Manual Function Testing:

• Validate that UI behaves as expected, based on a set of specified test cases.

Regression Testing:

• Documented test cases can be executed as needed to ensure that enhancement requests and/or API changes do not break existing application functionality.

Performance Testing:

• Available to be re-run against Test environment as needed.