Hina Irshad BITF06A004 Fizza Ghazanfer BITF06A024

2. Hina Irshad BITF06A004 Fizza Ghazanfer BITF06A024 Humna Yousaf BITF06A043 Qasim Zia BITF06A044

3. Chapter #7

4. Test Planning and preparation

5. Test planning: goals, strategies, and techniques. • Overall objectives and goals • Objects to be tested and the specific focus • Testing models and test cases • Information source identification and data collection • Analysis and initial model construction

6. Model verification and incremental improvement • Static test cases  • Dynamic test cases • Test suite preparation and management • Regression testing • On-the-Fly  test cases • Preparation of test procedure

7. Dependencies • Defect  detection  related  sequencing • Sequences to  avoid  accidents • Problem  diagnosis  related  sequencing • Natural grouping of test cases

8. Test Execution,Result Checking,And Measurement

9. Gerenal steps in test execution include: 1.Allocating test time and resources: 2.Invoking and running tests,and collecting execution information and measurements; 3.Checking testing results and identifyng system failures.

10. Failed Test Run: The key in handling failed test runs is to ensure that they will not block the execution of other test cases.there will be test run related to the re-verification of fixed problems.

11. Time Allocation and Management Test time allocation and management are closely related to people’s rples and responsiblity in carrying out specific testing activites.Managing other test resources.

12. Result checking: also known as The oracle problem The fact that software can fail in innumberale variations,the unexpected behavior can happen in truly unexpected ways,makes result checking difficult or nearly impossible.hence result checking or the oracle problem is a difficult taks,because of both theoretical difficulties and parctical limitations.

13. Analysis And Follow-up The third group of major test activites is analysis and follow-up after test execution. Analysis of indvidual test run includes result checking and failure identification.

14. This activity may involve these steps 1.Understanding the problem by studying the execution record,particularly thoes involving failures. 2.This is imporatant to confirm the problems and rule out possiblities of transient problem due to envoirmental disturbances or user errors. 3.Problem diagnosis to examine what kind of problem it is,where when and possible causes. it may involve analyzing the above records or some daignostic tool.

15. 4.Fault locating,to identify the exact location of fault baced on information from the previous steps and product knowledge. 5.Defect fixing,to fix located fauts by adding,removing,or correcting certain parts of code.

16. Analysis and follow-up for overall testing results 1.Reliability analysis for usage-based testing.which can be used to assess current product reliability and as input to determine if the pre-set relibility goal has been achived. 2.Coverage analysis for coverage based testing,which can be used as a surrogate for reliability and used as the stopping criterion or as input to various decisions related to testing management

17. Activities,people and Management

18. in this section,we will examine people’s role and responsibilties in test activites as well as related management issues.

19. Informal Vs Formal Testing Informal testing: One simple way to test the software is to just run it and observe its behavior.it is informal testing.

20. Testing of any software depends upon the software management.there are various problems related to software management where the best experienced and skilled people are assinged to testing group. this problem can be correct by a good knowledge of the technicalskills and experience involved in testing.

21. Formal testing: To satisfy customers,we need to model the software systems,their operational envoirnment,their usage scenarios,sequences,and patterns such that systematic testing can be performed to ensure that these systems satisfies their customer quality expectations.this testing is done by testing experts.

22. Testing teams can be organized into differtent structures i.e • Vertical model • Horizontal model

23. Vertical model: Where dedicated people perform one or more testing task for the product.one or more team can perform all the different types of testing i.e from unit testing to acceptance testing.

24. Horizontal model: Where testing team perform only one kind of testing for many different products within the organization.

25. Expert Participants: (Users and thirdparty testers) Besides the above internal participants,external participants or users may also be involved in testing.

26. In general,the users view and perspective may be needed to captuer in some scenarios,sequences or patterns to ensure satisfaction,reliability and performance.

27. Test Automation

28. Test automation aims to automate some manual tasks with the use of some manual tools.The demand for test automation is strong,because peurly manual testing from start to end can be error prone and tedious.

29. Issues those include in automation testing • Specific need and potential for automation. • Selection of existing tools • Possibility and cost constructing specific test automation tools • availablity of user training fot these tools/and time needed. • Overall cost,including costs of tool acquisiation,support training and usage. • Impact on resources,schedule,and project managment.

30. Automation for test execution Among the three major test activities,prepration,execution and follow-up execution is prime candidate for automation. for example,there were so many testing tools thoes allows tester to reset variable values execution states while test execution to check different behaviors of software at dynamic values.these was involvment of tester while testing execution process thats why ther are called semi automation tools.

31. in this modern age test automation tools can be considerd as enhanced debuggers that work for larger products,automate more indvidual testing activities and are generally more flexible and more tailorable than earlier debuggers.

32. Automation for planning and preparation Automation planning: Test planning and preparation,the potential for automation is different subactivities. The overall planning can only be carried out by experienced personal with expertiesin planning and management as well as good understanding of testing and development technologies.

33. Automation preparation: Test case preparation is the area where there is some realistic potenial for automation.for example in legacy products, various automated analysis can be perform to compare the current version of product with its previous version,and to screen the existing test suites to select the ones for regression testing.

34. In general test scripts and test cases are based on some formal models.the model construction for different test techniques requires high level of human intellgence and experties,and is therfore not easily automated.however some indvidual steps in model construction can be automated.such as automatic data gathering,graphical or other aids of modling.

35. Automation for test measurement analysis and follow-up In terms of analyses test results anf follow up actions the situation is similar to test planning and preparation.most of the follow up actions involves problem fixing and various other remidial and improvment initiatives very little of which can be automated.however specific analysis activities can be supported by various analysis and modeling tools.

36. Coverage analysis usually involves the use of more detailed information and measuerment data than that for reliablity analysis.But fortunately many coverage analysis tools exist to collect coverage information during testing execution.for example,serveral popular commercial testing tools collect and analyze coverage information to provide feedback and quality asessment to the testing process and overall development process.

37. McCabe test from McCabe and Associate provides control flow coverage related information ana analysis. • S-TCAT(system test coverage analysis tool) From SRI(software reserach inc)provide function level coverage and call pair information. • ATAC(automatic test analysis for C)from telecodia is a data flow coverage analysis tool for white box testing.