Topic: System Testing Cycles

System Testing Cycles:

The main thrust of the approach is to intensively test the front end in the first two releases, thus raising approximately 80% of errors in this period. With the majority of these errors fixed, standard and/or frequently used actions will be tested to prove individual elements and total system processing in Release v0.3. Regression testing of outstanding errors will be performed on an ongoing basis.

When all errors (which potentially impact overall processing) are fixed, an additional set of test cases are processed in Release v0.4 to ensure the system works in an integrated manner. It is intended that Release v0.4 be the final proving of the system as a single application. There should be no A or B class errors outstanding prior to the start of Release v0.4 testing.

Test Cases by Release version:

Testing by Phase
	Acceptance 1
Release v0.1	Functional 1
	User Acceptance
	Acceptance 2
Release v0.2	Functional 2
	Regression 1
	Acceptance 3
	Functional 3
Release v0.3	Performance 1
	Bash & Multi-User Testing
	Regression 1
	Regression 2
	Integration 1
	Technical 1
Release v0.4	Regression 1
	Regression 2
	Regression 3
	Installation Test
Contingency	Per Bug Fix Test Only