Innosphere Testing Process Overview

The Innosphere Testing Process (ITP) is a risk based, customizable, and technology independent methodology for testing software applications. Test Reports and Issue Reports allow management to assess the readiness of the product for release. They are also used to facilitate testing analysis and process improvement. The key to process improvement is our Understand-Plan-Act-Review cycle. We are constantly reviewing the results of our actions and creating betters plan for the next cycle.

The Innosphere Testing Process (ITP) contains our Core Processes which are indicated in the diagram below. The Core Processes are the foundation of Test Progam and support Manual Testing, Automated Testing, and Performance Testing.

Requirements: Requirements Management is typically the most difficult and problematic aspect of software development. Understanding what customers require is critical to project success. If a Waterfall methodology is being used Test Cases are developed based on the provided requirements to ensure testability. If an Agile methodology is being used Acceptance Tests are developed based on User Stories. 

Test Plan: A Test Plan is developed that describes the test program, timelines, resources, and tests to be performed for the test cycle leading to the release of a product.

Test Suites: Test Suites are groupings of similar Test Cases that are used to plan and manage the testing process.

Test Cases: Test Cases describe the tests to be executed. Tests may be Manual, Automated, Performance or a combination of all three. Manual Tests may be Structured or Unstructured using Exploratory Testing or a combination of either.

Test Tasks: A Test Task is any task that must be carried out in order to implement the Test Plan. It may be a Test Case that is assigned to a tester for execution on a specific configuration.

Issue Tracking: Issues or defects discovered through test execution are entered and tracked to resolution.

Test Reports: Test Reports are generated that indicate what has been tested and what remains to be tested.

Issue Reports: Issue Reports are generated that provide metrics regarding both outstanding and resolved issues. 

Retrospective: If an Agile methodology is being used a Retrospective is conducted following each iteration. If a Waterfall methodology is being used a Project Post Mortem is conducted at the end of the project. The purpose of the Retrospective or Post Mortem is to review what happened, what worked, and what did not work. This information is used to make improvements for planning the next iteration or project.

Project Management: Project Management is central to all the Core Processes.