The document provides an overview of software testing, including why it is important, common terminology, and different testing techniques. It discusses black box testing, which focuses on testing functional requirements without knowledge of internal structure. White box testing uses knowledge of internal structure to detect errors. Gray box testing combines aspects of both black box and white box testing. The document also covers test design targets and techniques like equivalence partitioning and boundary value analysis for black box testing, and code coverage analysis, data flow testing and error handling for white box testing.

1. Software Testing – Day One _____________________________________ By Govardhan Reddy M

2. Agenda Software Testing Why?

3. Purpose?

4. Terminologies? Notes Test Design Targets

5. Techniques Black Box

6. White Box

7. Gray Box

8. Software Testing Process of executing an application with the intent of finding bugs.

9. Process of demonstrating that errors are not present.

10. Process of establishing confidence that a program does what it is supposed to do.

11. Software Testing - Why... Here are some important defects that bettter testing would have found. In October 1999 the $125 million NASA Mars Climate Orbiter – an interplanetary weather satellite was lost in space due to a data conversion error. Investigators discovered that the software on the spacecraft performed certain calculations in English units (yards) when it should have used metric units (meters). (Cont...)

12. Software Testing - Why... In June 1996 the first flight of the European Space Agency's Ariane 5 rocket failed shortly after launching, resulting in an uninsured loss of $500,000,000. The disaster was traced to the lack of exception handling for a floating-point error when a 64-bit integer was converted to a 16-bit signed integer.

13. Software Testing - Purpose... Verification

14. Validation

15. Error Finding

16. Software Testing - Purpose... Verification Whether we built the project right?

17. Typically involves reviews and meetings to evaluate: Documents, Plans, Code, Requirements & Specifications. Can be done with: Checklists, Issues lists, walkthrouhs and inspection meetings.

18. Software Testing - Purpose... Validation Whether we built the right project?

19. Typically involves actual testing.

20. Tasks are designed to ensure that Internal design is valid.

21. Meets user expectations / business requirements. Validation takes place after verifications.

22. Software Testing - Purpose... Error Finding Failure points of the application. Failure: Variance between expected and actual result. Defects introduced in the: SRS: Software Requirement Specification.

23. PRD: Product Requirement Document.

24. FDD: Funtional/Feature Design Document.

25. Software Testing - Terminologies... Error: Discrepancy between expected and actual result.

26. Flaws that exists due to improper coding.

27. Undesirable output which negates the requirement.

28. Occurs in the syntax level (syntax error).

29. Error could be in: Environment

30. Application

31. Resource associated with testbed setup.

32. Software Testing - Terminologies... Bug: Error found before the application goes into production. Defect: Error found after the application goes into production.

33. Software Testing - Terminologies... Note: Error can be at any stage: Development

34. QA

35. After Release Error can be a Bug or Defect.

36. Software Testing - Terminologies... Test Strategy: An elaborate and systematic plan of action.

37. High level system wide expression of major activities that collectively achieve the overall desired result.

38. Identifies Risks, Constraints and Exposures present.

39. Introduces significant added value to the plan.

40. Software Testing - Terminologies... Test Strategy: Cont... Statements are expressed in high level terms of Physical components and activities.

41. Resources (People and Machines).

42. Types and Levels of Testing.

43. Schedules. Plan will be specific to the system being developed.

44. Software Testing - Terminologies... Test Plan: Collection of test cases.