|
Send us your Documentation
Tips,
so that we can publish them here...
Important areas of "black box" when QA engineer
write test plans:
* Acceptance test (into testing)
* Data flow and integrity
* Configuration and compatibility
* Stress test
* Regressions
* Performance
* Potential bugs
* Beta tests
* Release tests
* Utility
* User interfaces
It is a good practice to have developers review test
cases after they have been written. Knowing design of the specific feature or product in whole, developers can
give you a valuable feedback on what is missing from test cases and should be added, what areas to pay more attention
while testing and even how to apply it Test cases should be updated based on gotten feedback.
How to create a Test Plan without docs?
1. Try to break up your huge application into modules
that are functionally independent.
2. Within each module you start with the functions one by one.
3. For a simple function write all possible test cases that arise to be tested, while using the application as
there are no specs.
4. In this way you could complete one function and in turn whole application.
5. To prepare test cases or plan make use of Excel sheet. Each sheet will define each function within the module.
This is best way to organize the test cases.
|
