About Testing Documents and Definetion

@Readers,

Here, I have given some common testing definetion about testing, which usually we need to refer most of the time in hurry when go for the interview. HAHAHAHAHA.......

hope this will helpful to me as well you guys also............

Following are the testing documents.

1. Test Policy - Comapany level : A high level document describing the principle approach and major objectives of the organization regarding testing.
2. Test Strategy - Company level : The objective of testing is to reduce the risks inherent in computer system. The strategy must address the risks and present a process that can reduce those risk or high level description of the test levels to be performed and the testing within those levels for an organization or programme.
3. Test Methodology - Project level : It incorporate both testing strategy and testing tactics. It means by which the test strategy is achieved.
4. Test Plan - Project level : A document describing the scope approach,resources and schedule of intended test activities. It identifies amongest others test items, the features to be tested, testing task, who will do each task, degree of tester independence, test environment, test design technique and entry and exit criteria to be used and the rationale for their choice and any risks requiring contingency planning.
5. Test Case- Project Level : A testcase is a set of test input, execution conditions (pre/post conditions) and expected results developed for a particular test objective.
6. Test Procedure : A document specifying a sequence of actions for the execution of test. Also knwon as test script or manual test script.
7. Defect Report -Project Level : A document reporting on any flaw in component or system that can cause the component / system to fail to perform its required function. (IEEE 829)
8. Test summary report - Project Level : A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. (IEEE 829)
9. Test objective : A test objective is what the test is to be validate. eg. performance, functionality etc.
10. Verification : A technique to ensure the system complies with organization standards and processess, relying on review and non executable methods.
11. Validation : Ensures that the system operates according to the plan by executing the system functions through a series of tests that can be observed and evaluated
12. Test Approach : Approach to testing, how it will ensure adequate testing which is detailed enough for test task estimation and to use testing technique
13. Testing : Software testing is process used to identify the correctness, completeness and quality of developed computer software
14. Test case adequacy criteria: The criteria for deciding if the testcase selected are adequate and appropriate
15. Test suspension and resumption criteria: when test should be suspended and when they can be resumed
16. Test stop criteria The criteria for deciding when testing should be stopped