Test Management - Intresting Questions

Test Management-Interesting questionsfor new comer

1.Why test - what is Testing?
Testing is a process used to help identify the correctness, completeness and quality of developed computer software.

2. System Testing myths and legends - What are they?
Myth1: There is no need to test
Myth2: If testing must be done; two weeks at the end of the project is sufficient for testing
Myth3: Re-testing is not necessary
Myth4: Any fool can test
Myth5: The last thing you want is users involved in test
Myth6: The V-model is too complicated

3.What are the Concepts for Application Test Management?
Testing should be pro-active following the V-model
Test execution can be a manual process
Test execution can be an automated process
It is possible to plan the start date for testing
It is not possible to accurately plan the end date of testing
Ending testing is through risk assessment
A fool with a tool is still a fool
Testing is not a diagnosis process
Testing is a triage process
Testing is expensive
Not testing, can be more expensive

4. What Test Principles do you Recommend?
• Test involvement early in the lifecycle - Test Architect Signs off Requirements - Test Architect Signs off Use Cases • Fail Fast - Identify failures early via core test scripts • All Test Phases have equal value - Each Test Phase has its own value add • RACI chart everything • Testing is a pro-active activity - Plan the Test - Test the Plan • Finding defects is good - Ignorance of faults in a non-conformant system is no excuse

5.Test Analysts - What is their Value Add?
Understand the system under test
Document Assumptions
Create and execute repeatable tests
Value add through negative testing
Contribute to Impact Analysis when assessing Changes
Contribute to the risk assessment when considering to end testing

6. What do Test Analysts Need?
Education
Test Environment
Test Tools
Access Requirements Traceability -

7. What is this about?
Tracing requirements to test cases
Tracing test cases to requirements
Should be a feature of the Test Asset Management tool
Automatic on-demand process
Pie chart reporting

8. What is involved in the Application Test Lifecycle?
Unit testing
Module testing
Component testing
Component integration testing
Subsystem testing
System testing
Functional testing
Technical integration testing
System integration testing
Non-functional testing
Integration testing
Regression testing
Model Office testing
User Acceptance testing

9. How to manage Risk Mitigation?
Identify risks before the adversity affects the project
Analyse risk data for interpretation by the project team
Plan actions for probability, magnitude & consequences
Track risks and actions, maintaining a risk register
Control risk action plan, correct plan deviations

10. What should the Test Team do?
Programme Management
Strong Change Management
Strict Configuration Control
Pro Active Scope Creep Management
Inclusion in the decision making process

11. What are the Test Team Deliverables
Test Plans
Test Script Planner
Test Scripts
Test Execution Results
Defect Reports