is no.of test cases written per day, sort of standard across different types of testing, say functional, performance? What is the number?

Is there a agreeable standard on test case productivity? across domains?

Thanks
Greg

Hi Greg,

The number of test cases that can be written on a day is determined by the test case point (TCP) estimation. In TCP analysis the complexity of the test case is identified and the time frames are fixed based on the complex. The test case can either be of type (1) simple (2) medium or (3) complex.

The complexity factor is determined by the following factors:

1. The number of steps
2. Interface with other test cases
3. Domain complexity
4. Integration with other devices such
5. Multi-lingual support
6. Interface with external application
7. Data driven
8. Check points
9. Interacting with ui components such as applets etc.,

The above factor depends on the application under test, the functional domain tested etc., based on the complexity nature the time line is fixed for writing and execution of the test cases.

Test case productivity is a term which means that how many test cases are executed on a day. Each and every company will have a certain standard saying that certain number of test cases will be executed or written of a day. The numbers are determined by the organization level benchmark (OLBM). They will arrive at the benchmark by comparing against the competitors or other projects of the same domain. The benchmark will differ from domain to domain as the functional requirements varies for each domain.

Hi Greg,
There is no such thing that we have to write a particular number of test cases.
Any application we test,we will go for
a) UI Test cases
b)Functional Test cases

If we are given any application,we will start writing test cases of UI and functional and we will proceed further.

Thats what i know regarding this.Please correct me,if i am wrong.

Thanks,
Krishna.
--The Undertaking of a New Action brings New Strength--

Avg test cases 21-25 per day and it speeds up accordingly to the tester expertness and domain knowledge.