Testing the application¶
Strategy¶
We have already established in the proposal that the application will be tested using a system of alpha, beta, and release testing. you should refer back to the testing section of the proposal to reconfirm the strategy. It's here at Test Strategy.
The easiest way to make sure that testing is effective is to define the tests to be completed at the design stage. As you introduce a feature or option into the design, how will you make sure that the application fulfills the Functional Requirements and meets the needs of the Client and the target end-users?
We create a test plan¶
The test plan is just what it says it is. It's a system that will be used to confirm success, or identify defects.
It is important to be specific in your plan, naming the items to be tested explicitly, and setting the order in which the tests will carried out. The second part is often important because one feature will often depend on a feature that was created before it. For example, the login process can't be tested until we know that the form used for authentication launches as required.
Remember, the brief tells us to make a plan that has a logical structure and sequence.
Here's the Test Plan we devised for Vectis Games in Activity A(ii):
The Test Log Template is provided with the project files and used in Task 2¶
You wan't see the template until the start of Task 2, but we can show the structure in the Test Log page of this section.