The document discusses test effort estimation which involves estimating the resources, time, and skills required to test a project. The test manager is typically responsible for test estimation. The steps include identifying components and test strategies, tasks, software size and complexity, and inputs to estimate test effort. The estimate is then used to prepare a test plan and validate the estimate after the project. Common techniques discussed are function point analysis, COCOMO model, and test point analysis.

1. Test Effort Estimation

2. Why Test Effort EstimationExpected Testing outcomeEffort

3. Estimate of what ??

4. ResourcesTimeSkill

5. Who does the Test Estimation?

6. “Test Manager”

7. Steps in Test Effort Estimation1234567

8. Identifying the Components to be Tested1

9. Common ComponentsGUI ControlsScreensFunctionsReports

10. Identifying a Test Strategy2

11. On what basis test strategies are formed?

12. Based on the components indentified

13. TestStrategy1Functionality1TestStrategy2TestStrategy3Functionality12TestStrategy4

14. Identifying the tasks to be performedOne time task

15. Repetitive activities3

16. One time tasksPreparing test strategyUnderstanding customer requirementsEstablishing communication planRepetitive tasks

17. Identifying test condition

18. Developing Test cases

19. Generating Test Data

20. Reviewing test condition, test case, test data

21. Executing test cases

22. Reporting test resultsComputing software sizeBased on complexity4

23. Levels of complexityLow complexity

24. Web applications

25. Desktop applications

26. Medium complexity

27. Two tier/three tier application

28. High complexity

29. Multitier applicationsEstimating Test Effort1INPUTS25Test EffortDurations

30. Infrastructure

31. Resources