Quality to me is

"Synergistic phenomena experienced by the user(s) when the product or a service satisfies the requirements, achieves business goals, exceeds expectations, is incredibly usable with real-time servicing & updates, optimal performance and cost effective"

Friday, August 17, 2007

Strategy for Testing an Existing Product

Discover Products Requirements
§ To know/identify what types/strategies of testing should be done
Define the importance of Quality to the Project
To determine how much time and effort would be required [ or can be applied] to testing
Define a test plan, including release criteria
§ To verify different people’s understanding about the product
§ To know when we are ready to ship

Test Case Review - Checklist

Test Case Review
The review should verify whether, the purpose, scope and the content of the test cases are correctly documented. These test cases cover all the positive and negative scenarios involved with the application and its performance.
o It should describe every input, action, or event and an expected response, to help determine if every feature / functionality of an application is working correctly.
o Proper understanding of requirements
o Impact areas are identified and brought under test
o Test data is correct and represent every possible class of the domain
o Test coverage is adequate

Steps To List Functional Testcases

I The derivation of Functional test cases and the mapping between them & the usecases
Needs -> Features -> Usecases/Support Specs -> Scenarios -> Testcases
II The use case mostly will list/have the following details
Brief description
Flow of events
Basic flow
Alternative flow 1
Alternative flow 2
Special requirements
Preconditions
Post-conditions
Extension points
Context diagram
Activity diagram