If you are Government did you look at the 40CFR guidelines on establishing testing granted its for the EPA and water - but can be extraplated to Applications (it may help) -
http://www.dec.state.ny.us/website/dow/bwp/ref750/40cfr136_b.html
Lets see - Pointe Technology has some very interesting whitepapers on Testing and establishing the procedures.
http://www.pointtechnology.com
Remember - Key testing Phases include:
- Package validation testing (when commercial business applications are being used do they integrate with existing systems)
- Unit testing (best accomplished during the development process by developers to validate program logic and to verify that the code is working according to specifications)
- Integration testing (for testing the combinations of individually unit-tested pieces of code as they are linked)
- System testing (consisting of the project team's final test of the system's functionality, performance, and appropriateness and demonstrating that the system meets the original objectives and requirements and that it works within the defined constraints)
- Systems integration testing (addressing integration with existing applications - purchased packages and legacy, internally developed software - as well as effective security, infrastructure, and network support/optimization)
- User acceptance testing (demonstrating that the application meets the original business objectives and satisfies the user and IT environment requirements; must involve end users)
As the development project moves through these events, the approach and focus of testing change. Items may be retested iteratively and multiple times through the approval process. The QA/QC team will utilize a review and sign-off approach at major points in the life cycle. These points include movement of code between development/unit testing into integration testing. When groups of code appear ready to graduate from the integration test into the system test, and then from the system test to user acceptance testing, users alone will not be solely responsible for sign-off. [i]Business users, functional teams, and project management will be involved in the approval at integration test, system test, and user acceptance test completion[/i]
Maybe a definition of what we seen as each testing phase was and do:
1. [b]Package validation testing:[/b] When commercial applications are in use. The package is evaluated to determine whether a) it is properly configured - b)performs correctly - c) identify any incompatibilities between the software package and the environment in which it will operate.
Results: Completion of this testing event indicates the package operates acceptably in the target environment. This testing is standard practice among organizations that have set up successful testing environments.
2. [b]Unit testing:[/b] It has two major objectives: a) to verify that the application software component's code works according to its specifications - b) to validate program logic.
Results: Pinpoints discrepancies between what an application software component does and what it is expected to do.
3. [b]Integration testing:[/b] Individually unit-tested pieces of code are tested as they are merged together.
Results: Uncovers errors that cannot be found during unit testing due to the errors occurring in the interactions and interfaces between units.
4. [b]System testing:[/b] Independent system's functionality, performance, and appropriateness.
Results: It shows that the system meets the original objectives and requirements and that it works within the defined constraints.
5. [b]System integration testing:[/b]Addresses integration of the system as a whole with existing applications, as well as effective security, infrastructure, and network support/optimization.
6. [b]User acceptance testing:[/b] Application meets the original business objectives and satisfies user and IT environment requirements.
Results: This test should validate that the system fits into the real-world business environment in which it will be used.
Can really tell you how to do it - but its mostly the establishment of processes - and procedures - What they will be testing for - why they are performing the Integration test - what should be tested - test reviews - test success criteria -
We are just starting to develop one - its going to be interesting ... selling it ... to the developers and business folks ...