📓Test Plan

Brief definition: Test Plan refers to a detailed document that catalogs the test strategy, objectives, schedule, estimations, deadlines, and the resources required for completing that particular project. (source: Browserstack). The following are the parts and the description of the test plan

1. Objectives - This contains the purpose and the scope of the test plan. Software's varies from each other, so it is important to set what would the team expects that the SQA will do. The following topic should be define in the part.

   1. Purpose

   2. Scope

   3. Limitation

2. Resource Allocation / Test Items - This part of the test plan contains the list of feature to be tested. Example:

3. Testing Strategy - Define the testing strategy approach that the QA used towards the application. Refer from the Testing types for the its list. Example: https://www.notion.so/highoutput/77f532bea4af481cbef35344eb7eb9f4?v=f2936807009a423ebc1a9931c879f8ce

4. Resources - Such as Test tools, Man power, Hardware, Specifications are define in this portion. 1. Test Tools - Define what tools are to be use on testing the application. Example:

   2. Man Power - Number of testers needed to execute this test plan Example: 3. Hardware - Sets of Hardware to use. This should be in accordance to the clients hardware agreements Example: 4. Specification - List of files, documents, images formats and software/hardware requirements when accessing features of the application. Example: -

Above are one example of the Test plan here in HOV. This documents varies its parts depends on what application thus the testers will gonna test. The important is to have this document be cleared and self describable to all members of the team.