HP0-M31 Quality Center Certification Preparation 3 - Test Plan Module

TEST PLAN

1. Developing a clear and concise test plan is fundamental to successful application testing. A good test plan enables you to assess the quality of your application at any point in the application management process.
2. Developing a test plan consists of the following: Define Testing Strategy, Define Test Subjects, Design Tests, Create Requirements Coverage, Design Test Steps, Automate Tests, Analyze Test Plan, Establish Baseline.
3. The test plan tree is a graphical representation of your test plan. It is a hierarchical list of tests organized according to topic, which describes the set of tests you will implement in order to meet your quality requirements.
4. You can link a test to specific defects.
5. You can include parameters in your manual tests. This enables you to run the same test repeatedly and assign the parameters different values.
6. Link each test in the test plan tree with a requirement or requirements in the requirements tree. By defining requirements coverage for a test, you can keep track of the relationship between the tests in your test plan and your original requirements.
7. For manual tests you define steps, execute them on your application, and record the results of each step. Use manual tests in cases where the test requires a response by the tester. Manual tests include usability tests, onetime tests, tests that need to be run immediately, tests requiring knowledge of the application, and tests without predictable results.
8. You can include a step that calls another manual test. This is useful if you have common steps that you want to perform as part of other tests.
9. Automating a test allows unattended execution of the test at high speed. It also makes the test reusable and repeatable.
10. We automate functional, benchmark, unit, stress and load tests, as well as tests requiring detailed information about applications. 
11. (Lets read more)

HP0-M31 Quality Center Certification Preparation 2 - Requirements Module

REQUIREMENTS

·         Requirements describe in detail what needs to be solved or achieved to meet the objectives of your application under development.

·         Not all fields and functionality in the Requirements module are available if you are working with the Starter Edition.

·         You use the requirements scope to determine the overall requirements for the application under development. You then define different groups of requirements based either on requirement type or functional area.  Requirement groups are recorded in the Requirements module by creating a requirements tree. The requirements tree is a graphical representation of your requirements specification, displaying the hierarchical relationship between different requirements.

·         For each requirement group, you create a list of detailed requirements in the requirements tree.

·         Each requirement in the tree is described in detail and can include any relevant attachments. You then assign the requirement a priority level which can be taken into consideration when creating the test plan.

·         After defining your requirements, you can add traceability between the requirements. When analyzing the impact of a change proposed in a specific requirement, traceability shows the other requirements that the change might affect.
(    Lets read more)