1. Test case point (TCP) analysis is an approach for doing an accurate estimation of functional testing projects.

The approach emphasizes on key testing factors that determine the complexity of the entire testing cycle and
gives a way of translating test creation efforts to test execution efforts. Test case points is a way of
representing the efforts involved in testing projects.

Different approach is followed for calculating the tcp in manual testing and automation testing.

TCP analysis uses a 7-step process

1. Identify use cases

2. Identify test cases
3. Determine TCP for test case generation
4. Determine TCP for automation
5. Determine TCP for manual execution
6. Determine TCP for automated execution
7. Determine total TCP test estimation is done by estimating the complexity of the test cases.

The complexity of the test cases falls under three categories: (1) simple (2) medium and (3) complexity. The
complexity factors are fixed based on the following categories:
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 timeline for creation and execution of the test cases depends on the time line fixed which contributes
towards the test case point analysis.

With this above you can calculate the time line needed for testing a search engine.

2. Testing Estimation depends upon the lines of code.

suppose 10LOC(LINES OF CODE)=1FP(Functiona point)

then 1000LOC=100FP
FP*3TECH(BVA,EP,Error guessing)=Test case
100FP*3=300TC

We can estimate 30Tc per a day

that means 300TC/30=10DAYS for writing the test cases

Testplan=1/2 of the test case prepartion that means=5 days

Test case execution=1 1/2 of the test case prepartion=15 days

Buffer time =20 days

the estimations depends on the following criteria:

1.Complexity of the project
2.System Configurations
3.Resource availability
4.Knowledge about the requirement, technology used in the project.
5.Number of modules

How do you plan testing effort

Hi,

You can plan testing efforts using various estimation methods like Function Point, Usecase Point, ROM(Rough Order
Margin).

The 1st 2 estimation techniques have process and formulas to calculate the efforts for any project. But the last one is
done based on the experience or having bulk of projects implemented on same technology and functionalities.

For any of this estimation; requirements should be in place and they should be either in the form of FR's (Functional
Requirements) or in UC's (Usecases) format.

If you want to do estimation using Function Points then you need to have FR's in place until these are not available the
estimation isn't possible.
The same way for UC estimation usecases should be available from them we can derive FR's and can calculate the UC
points. If UC's are not available then from the available FR's also we can extract or combine into usecase and can derive
the UC efforts

Apart from these the 3rd and general estimation also can be used based on the experience, that is ROM. Efforts derived
from these will be approximate not accurate.

For any of the above estimation techniques you will be adding a some amount of buffer to the final estimation.

For ex: If any requirements are not available then how do you estimate test efforts for that project.

In this case either you have to go with your experience or with rough estimates considering the technology and criticality
of the requirements. In this case your efforts planned may be sufficient or may overshoot or may be short to accomplish
the testing.

Generally industry standards are ranging from 25 to 30% of efforts from whole project efforts (called as engineering
efforts).

If the project is Fixed Cost then you should be good bargainer in gaining the test efforts, becoz the reason is even after
your correct estimation also sometimes dev team will not be ready for accommodating them to you. So in that case you
should be efficient in gaining the test efforts by showing the past historical data and results.

If it is Time and Material Project then you will not have problem in the efforts accommodated. There will be period of
duration and efforts planned for that.

: Automation Effort Estimation Process

1. Descriptve programming or Object repository method.

2. New script or modification of existing script.
3. What functionalities and gui features to be automated.
4. Do we need to verify the database.
5. Number of pages, text fields, drop downs.
6. Any additional addins to be used. (addins need to be purchased if required)