Showing posts with label Test Cases. Show all posts
Showing posts with label Test Cases. Show all posts

Monday, April 4, 2011

Test case for any Object & Electric Item

Hey Friends,

We are facing so many interviews with questions like, try to write test case for pen, paper, bottle, mobile, washing machine, coffee machine, fan etc. But when they ask, we only explain whatever at that time in our mind. Here I give some tips for the answer of this question, For almost any object we can give some cases common like

  1. Look and Feel: Colour, height, design, width, Material etc
  2. Performance: durability, continuous perform or not
  3. Usability: Easy to use, accessibility etc
  4. Rigidity: How strong, how work in abnormal condition etc.
  5. Configuration: how configure the machine,
  6. Functionality: how it function with each switch n function
  7. Security: how secure that machine or item

For example, if Pen is given, then for pen you can say:

what is the color of pen? which color ink with it? what is the material of pen either rubber, plastic ? which brand's pen? is all the spell and information on pen is proper or not? how easy to use that pen? when you write can you able to write it continuous or not ? If you through it, then it will break or not? if you hit it then also its able to write or not? how long you are able to write ? etc etc.

Hope this will help you to write or give answer of such kind of questions. If you find anything new, then please update it in comments so we can get all information at one place.


Sunday, March 20, 2011

Prioritization of tests


Prioritization of tests
Hey folks,
Always Testers get less time to test the application, in this type of situation, one must take a decision to prioritization of his test. Here are some points we can take in consideration for prioritize it. If you found some more please add in comments, so all can get good information. I try my best to give you good information, hope you guys like it.

Principle
Prioritize tests So that, whenever you stop testing, you have done the best testing In the time available.

  • How to Prioritize
  • Possible ranking criteria
  • Test where a failure would be:
  • most severe
  • more visible
  • More likely
  • Ask the customer to prioritize the requirements
  • Critical to customer’s business
  • Areas changed most often
  • Areas with most problems in the past
  • Most complex areas, or technically critical 

Monday, June 21, 2010

Guidelines to review Test cases


Guidelines to review Test cases

  1. Check all the requirements covered or not
  2. Check no major scenario is missing
  3. Check test step is written complete and understandable
  4. Clear expected results is mentioned for each step
  5. Check all text and grammar mistake
  6. Flow of test step is appropriate
  7. Information related to setup of test environment like pre requisites, what are success/failed , end conditions etc
  8. Check is there any invalid test cases
  9. Check is there any redundancy in test cases
  10. Check priority of test cases
  11. Check narration of test cases
  12. Test cases follow agreed standard format
  13. The Test cases are complete with respect to the Specifications Document on which they are based
  14. Test data is mentioned explicitly for each test condition
  15. Pre-conditions for executing a test case or a set of test cases are specified