The test plan is comprised of test procedures to verify correct behavior of the application being tested.
You must have a github account, so you can clone repositories and submit/track issues that you find.
Ideally, the test plan is created by QA or the tester and reviewed by the developer for completeness, after QA gets a description of the new feature or thing to be tested. Less ideally, the test plan is created by the developer and reviewed by QA or the tester to try to catch edge-cases the developer didn't think about testing.
If we need or want to re-test something later, old test plans will be cloned or edited.
- Fork this mastercoin-MSC/QA repository.
- Create a subdirectory in the TestPlans directory of your fork for the application to be tested, e.g. OmniWallet.
- Copy the appropriate test requirements file(s) from the TestRequirements directory into the newly created application directory.
- Edit each test procedure to tailor the steps for the application to be tested. Be as explicit as possible. You can use TestPlanSkeleton.md as a template.
- Include steps to initialize the test environment to a known state.
- Make sure you verify that each action by the user produces the correct behavior and result by the application.
- Include steps to return the environment to a known state after test completion.
- Feel free to add test procedures, especially for aspects specific to the application you are testing.
You may want to put each customized test procedure in its own file.
Follow the procedure in TestPlanExecution.md to carry out the test plan.
Some tests will take a long time to complete. You can run multiple tests simultaneously as long as they don't conflict with each other.
Report results as you get them (whether from other testers or from your own tests) by filling out the
MSC Client Test Results Reporting Form.