Test plan is a high level document which explains the test strategy,time lines and available resources in detail.Typically a test plan contains: -Objective -Test strategy -Resources -Entry criteria -Exit criteria -Use cases/Test cases -Tasks -Features to be tested and not tested -Risks/Assumptions.
What if the software is so buggy it can't really be tested at all?
How can it be known when to stop testing?
How can Software QA processes be implemented without stifling productivity?
What if an organization is growing so fast that fixed QA processes are impossible?
How does a client/server environment affect testing?
How can World Wide Web sites be tested?
Differentiate top-down and bottom-up approach.
What is structural testing and what is functional testing?
Validation and Verification. What are they?
How to differentiate Bugs, Error and Defect?
