Do You Have a Hit List? Presented by Md. Maftahur Rahman Senior SQA Engineer Enosis Solutions
Analysis & Design Total Time Development Testing Analysis & Design Development Testing Analysis & Design Development Testing Why Hit List? Conventional approach… Initial PhaseN Phase2
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?
These are my Test Cases Time Task/Test Cases Which one will be executed? Now he goes to execute the test cases
What will he do now? Will he start pulling his hair?
Can’t we break the conventional approach… Can’t we adjust the time? Can’t we be like…
I don’t care, I’m Hit Man Here is my Hit List Hit List
Time is not enough to execute all those plans
I have a simplified Hit List
I’m bang on target
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?