The document discusses the concept of a "hit list" for software testing. It suggests creating a prioritized list of the most critical and common types of tests to focus testing efforts, rather than trying to test all possible test cases. This hit list would include things like data type errors, data limits, special characters, and connectivity issues. Maintaining a written or mental hit list of these high-priority test areas allows a tester to quickly uncover bugs within a limited testing time frame.
1. Do You Have a Hit List? Presented by Md. Maftahur Rahman Senior SQA Engineer Enosis Solutions
2. Analysis & Design Total Time Development Testing Analysis & Design Development Testing Analysis & Design Development Testing Why Hit List? Conventional approach… Initial PhaseN Phase2
3. System shouldn’t crash Price calculation is OK Value formatted properly It doesn’t lose data OK, I’ll cover these in test cases … . Lots of …. What does tester think?
4. These are my Test Cases Time Task/Test Cases Which one will be executed? Now he goes to execute the test cases
5. What will he do now? Will he start pulling his hair?
6. Can’t we break the conventional approach… Can’t we adjust the time? Can’t we be like…
7.
8. That’s why the concept of Hit List. a) Context Dependent Key Points : Two types of content: Remains unchanged throughout the application Example: Fixed format of Price, Acc No, Title, frequent occurring of critical bug,…, etc. Should have leading zeros Should be like 0000 13980.5 0 What will be there?
