Test Strategy and Planning

University IT will meet with you to review system changes, implementation timeline, and resource availability in order to create and implement a test strategy for your application. The test strategy may include any of the following:

  • Use case identification
  • Automated testing (regression, load, stress, or performance testing)
  • Exploratory testing
  • Manual testing
  • Browser emulation

Use Case Identification

University IT will identify meaningful user stories that can be translated into use cases for testing. Use cases should identify the type of user and area to be tested. When possible, they should also include inputs, expected outputs, and variations.

Exploratory Testing

University IT will identify meaningful areas of exploration and then explore functionality within those areas looking for behavior that is counter to either user expectations or known system behavior. This testing may be executed by you, your application’s users, or University IT.

Manual Testing

University IT will help schedule and coordinate testing based on identified use cases. This testing may be executed by you, your application’s users, or University IT. University IT will review the results with the full testing team and discuss options for any necessary remediation.

Automated Testing

University IT will write testing scripts to automate testing of identified use cases for regression, load, stress, and/or performance review. These tests must be maintained as changes are applied to the application environment and can either be scheduled to run at set times or per diem. These tests are currently targeted at browser-based applications, but University IT is willing to try client-based testing scripts.

Browser Emulation

University IT can execute tests of a browser-based application using software that emulates a variety of current web browsers.