Authoring Test Cases for Real World Entities - Test Cases of a "Kinley" Water Bottle

Introduction :

Since my career took off in Testing domain, I have been authoring test cases for various domains, platforms, technologies and under different methodologies. I felt like authoring test cases is similar for these and worthy. What I have come to know is there shall be a blue print to author test cases again considering the project constraints (Time, Cost and Effort) where the emphasize is towards.
The step by step approach towards authoring test cases was similar with minor deviations in case of availability or no availability of documents to refer while drafting.

Approach :
I would follow these steps to draft the test cases, which are as follows,
(1) Analyze the Real World entity.
(2) Understand objectivity (functionality).
(3) Identify the functional points
(4) Identify Test Conditions.
(5) Prepare Test Scenarios.
(6) Author test cases.

Detailed Explanation :
Analyze : Check the existing information pertaining to entity, could be anything. If a sample is available would be appropriate to give a look. Check for the shape, size and look and feel of the entity.

Understand Objectivity : By analyzing the entity we would draw certain conclusion about its behavior, our sense of knowledge will be help us understand the object better.

Identify the Functional Points : As we come to know the behavior of the application, the uniqueness with respect to the behavior will be known. Hence its required to check for uniqueness of the functional point.

Identify Test Conditions : The dependencies or rules and regulations which are associated with the functional points are nothing but Test Conditions.

Prepare Test Scenarios :The unique functional flow of the system is to be identified (functional points) and brief description of the flow with associated participants(Actors), data effecting and list of conditions are to be drafted. Test Scenarios help in decomposing the functionality into various Test Levels.

Author Test Cases: Test cases can be drafted from easily from the conditions and scenarios. It’s good to choose a typical test cases template to draft the test cases.

Example: Testing a "Kinley" water Bottle

As we are not provided with any specific requirements we assume default requirements as the base.

My intention in choosing real world entities as Test objects is that, we are aware of the functionality of the real world objects thus have better understanding of the object and can draft test cases easily.

Following the Approach to Test,

(1) Analyze the Water Bottle:
Give a closer look to the water bottle from top to bottom and finalize certain things like,
Bottle cap, Seal, Label of the manufacturer – Typical Static Testing

(2) Understand objectivity:
Typically a Kinley water bottle is used to store, use drinking water.

(3) Identify the functional points:

Functional points would be
- Cap of the bottle
- Bottle trunk

(4) Identify Test Conditions:

Test conditions would be

  • Cap shall be open
  • Water shall be filled
  • Bottle shall be lifted to drink
  • Water in the bottle and capacity of the bottle when full shall match …
(5) Prepare Test Scenarios:
  • Bottle with cap
  • Bottle without cap
  • Label Details
  • Bottle with water
  • Bottle without water
(6) Author test cases:

Test cases are to be drafted with references to requirements, Functional Points, Test Conditions, Test Scenarios.

Unit:
  1. Cap, Water, bottle, label, etc … shall be tested separately
Integration:
  1. Each individual unit shall be integrated and tested.
  2. Water poured into bottle with cap,
  3. Water poured into bottle without cap
  4. Bottle with label, cap and water,
  5. Bottle without label, with cap and water,
  6. Bottle without label, without cap and water,
  7. Bottle without label, cap and water, all possible combination
System :
  1. The complete bottle shall be assembled and tested from end-end against the requirements.

UAT:
  1. The bottle from user’s perspective shall be tested for various quality factors



Thanks & Regards ,

Prashant Vadher | QA Engineer

1 Comments:

Tanmay Patel said...
This comment has been removed by a blog administrator.

Post a Comment

 
Design by Prashant Vadher