Test Estimate in Agile


Estimation of TC's:
==============
The below points are laid down based on the acceptance criteria, one point corresponding to

1. UI changes -> its an 1-1, which implies for a corresponding change in UI, TC needs to be prepared.
2. Function changes -> its based on the complexity breakdown / based on breakdown of functionality from Top to bottom approach should be followed in identifying the no of TC's to be prepared.
3. For DB changes -> Based on complexity of impact, it can be a 1-1 or 1-many.
4. Settings/Parameter which effect in combinations -> combination of settings w.r.t their impact should be used for TC preparation.

Based on the above way, we can estimate the TC count that shall be prepared.

What should be the order/ best way to prepare TC's?
1. Firstly Understand the workflow identify the Happy Path i.e., positive flow
2. Secondly identify the Standard things that should be in place
3. Thirdly identify the Negative paths.
4. Finally identify the boundaries

What can be an ideal percentage of effort days that be used by teams in any feature development?

25% effort can be spent on Analysis; 50% for Design, Development and Unit Test; remaining 25% for testing.


.

Comments

Popular posts from this blog

QA's approach 2 Java - Understanding Static context

QA's approach 2 Java - Collections Framework & Generics Introduction

Technologies - Log4J - Create Log4j Configuration File - Where ? How ? What ?