Creating Test Plans In Microsoft Test Manager

Explanation
Creating test cases before creating a test plan is not a best practice. The test plan outlines the overall approach and strategy for testing, including the objectives, scope, deliverables, and timelines. It provides a high-level overview of the testing process. On the other hand, test cases are specific scenarios or conditions that need to be tested. They are derived from the test plan and outline the steps, inputs, and expected outputs for each test. Therefore, it is important to first create a test plan and then derive test cases from it.

Explanation
Test cases can be reused in multiple test plans. Reusing test cases helps in saving time and effort as the same test cases can be used for different test scenarios or test plans. This also ensures consistency in testing across different plans. Therefore, the statement "Test Cases cannot be used in more than one Test Plan" is false.

Explanation
A Test Plan is a detailed document that outlines the objectives, scope, approach, and schedule of a testing project. It is not limited to the individual who created it, but rather serves as a guide for the entire testing team. Multiple team members can refer to and use the Test Plan to understand the testing requirements, strategies, and goals. Therefore, the statement that a Test Plan can only be used by the individual who created it is false.

Explanation
Test cases should be assigned to a test plan for proper reporting and tracking. This helps in organizing and managing the testing process effectively. Assigning test cases to a test plan ensures that all the necessary tests are identified, documented, and executed. It also allows for better tracking of the progress and status of testing activities. By associating test cases with a test plan, it becomes easier to identify which tests have been completed, which are pending, and which need to be retested. This helps in ensuring comprehensive test coverage and enables efficient reporting of test results.

Explanation
It is considered a best practice for each planned test iteration to have its own test plan because it allows for better organization and tracking of testing activities. Having a separate test plan for each iteration ensures that the specific objectives, scope, and test cases for that iteration are clearly defined. It also allows for easier identification and resolution of any issues or risks that may arise during testing. Additionally, having separate test plans helps in accurately measuring the progress and effectiveness of each iteration, making it easier to evaluate the overall success of the testing process.