This page presents the phases, deliverables, roles, and tasks for a full performance test project that makes use of several industry best practices and tools for load testing and performance engineering one of the activities for capacity management of IT Service Management (ITSM).
The Test Handbook is a framework document which describes the test steps to be excuted to address risks which should be covered by software testing. The test concept describes the test steps and test activities to be executed for a particular project.The test step plan details the procedure for a test step and describes implementation of the test concept for a particular test step.During speed testing, the user response time (latency) of each user action is measured.The script for each action will look for some text on each resulting page to confirm that the intended result appears as designed.Since speed testing is usually the first performance test to be performed, issues from installation and configuration are identified during this step.
Because this form of performance testing is performed for a single user (under no other load), this form of testing exposes issues with the adequacy of CPU, disk I/O access and data transfer speeds, and database access optimizations.
The performance speed profile of an application obtained during speed testing include the time to manually start-up and stop the application on its servers.
After prototyping, and after the product goes though the Design Refinement cycle when engineers revise and improve the design to meet performance and design requirements and specifications, objective, comprehensive Design Verification Testing (DVT) is performed to verify all product specifications, interface standards, OEM requirements, and diagnostic commands.
Process (or Pilot) Verification Test (PVT) is a subset of Design Verification Tests (DVT) performed on pre-production or production units to Verify that the design has been correctly implemented into production.
The Test Policy is the document which describes an organization's philosophy towards the testing (or quality assurance) of software.
The test policy is complementary to, or a component of, the organization's Quality Policy, which describes the basic views and aims of a company, regarding quality, as pursued by management.