Tag Info

New answers tagged

0

Below are the components of a test plan, which should be included. 1. Summary 1.1. Introduction - Provide an overview of this document in this section 1.2. Scope of testing - The scope of testing needs to be clearly defined. The plan should define items / features that are in scope or out of scope for the testing phase. - 1.2.1. **Features To be tested** ...


2

What are the most important components/parts of a well-written test plan document for a testing project. Consider you are testing a Financial web app. As per IEEE 829 standards, the components of a Test Plan document should be : Test Plan identifier References Introduction Test Items Risks Items to be tested Features excluded for testing Testing ...


0

For the part of your question "Also we have separate sections for Features to be tested and not to be tested. Is this not redundant with features to be tested? Also if we indicate the list of features not to be tested, why we need to indicate the list f features to be tested? When features are listed in requirement document, obviously all of ...


4

Yes, you can do that. For this you need to save your common/shared test steps in a new test case and then change it to a template using 'Mark as Template Test'. Then where ever you need these shared steps, open that test case and in the test step section of that case select the option 'Call to Test' and then select the shared test case template which you ...


0

You might consider using a mind map instead of a traditional test plan. It will provide you a document artifact and be lighter weight since your project is medium sized. People can still collaborate on it if need be by adding / updating nodes. xmind or freemind are pretty popular choices.



Top 50 recent answers are included