This document discusses present problems and future solutions in software testing. It identifies several challenges in testing including determining when enough testing has been done, estimating testing time requirements, and a lack of innovation in the field. The document proposes future solutions like integrated testing environments, automated regression selection tools, and representing test cases in a visual format. It envisions testing frameworks that are tool-driven, integrated with development, and leveraging diverse sources of information.

1. 1Software Testing – Present Problems and Future SolutionsVipul Kocher

2. 2Science Fiction – Fiction today, Reality tomorrowArthur C. Clark Geosynchronous satellites (1945) – Actual satellites (1963)Cloning - DollyJules Verne’s “Twenty Thousand leagues under the sea” (1869) – Simon Lake built “Argonaut” first submarine to operate in the open seas (1897)

3. 3What About These?Androids TimeTeleportationWhat about ? travel? ? How about self testing code? May that never become a reality as long as I live…

4. 4assumptions

5. 5AssumptionsAll future solutions are based on today’s technologies

6. Disruptiveinnovationslike new class of operating systems, development paradigms, languages may significantly alter the landscapes6AssumptionsI have a few ideas on new class of Operating Systems

7. new class of programming languages and paradigms to support that operating system

8. ultimately supported by new class of hardwareI have no clue about it !

9. 7problems in testing

10. 8Problems in TestingAre there problemsin testing? We all seem to be doing fine!Probably the biggest problem in testing is-“we do not have a problem”

11. 9Problems in TestingWhy is this aproblem? Is there a solution in future?Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Albert Einstein

12. 10challenges in testing

13. 11Challenges in Testing What does testing mean for different stakeholders?

14. Have we tested enough?

15. How much time do I need to test it?

16. How many test cases should I write?

17. Oracle problem

18. How do I choose right set of regression tests?

19. How do I get developers to do better testing?

20. Do I need coding skills? What will I do with those?

21. How do I teaching testing to my testers?12What does testing mean for different stakeholders

22. 13What does testing mean for different stakeholders?Let us face itNobody wants testing…

23. 14What does testing mean for different stakeholders?If one assumes that “testing is necessary” one is likely to try to improve the way testing gets doneIf one believes that testing is unnecessary then one is more likely to find ways to minimize or eliminate testingMindset Matters !

24. 15testing world’s biggest problem

25. 16Testing World’s biggest problemWhere is the innovationin testing?

26. Innovation as in Breakthrough Innovation?17Testing World’s biggest problemCan you name three breakthrough innovations in testing? At least one?Where does the future of testing lie?

27. 18HITEEHITHave I Tested Enough Do you have a bulletproof answer?

28. 19HITEFirst define “ENOUGH” – Today - No catastrophic or critical or major failure for usersTomorrow - ?20HITEIntegrated software status monitor- Explained later (Patent Pending)

29. New software technology- Self monitoring (Patent Pending), Self healing systems

30. Software testing as a distributed, automated service - you pay software companies to install software on your system and test it (Patent Pending)21How much time do I need to test it

31. 22How much time do I need to test itWhat are the problems you face in answering this question?What are the solutions today? Estimation techniques? Work Breakdown Structure? Function Points? Test Points? Use Case Points?

32. Historical Data? Rule of thumb? Gut feel?Are these accurate? What aboutDifferent levels of quality, workmanship (developers and testers both), project constraints such as budget, time and Subsequent Regression Cycles?Future solution A mechanism to define quality level and a mechanism to measure that level (Patent Pending)

33. Collection and analysis of data in automated manner and predictions based on current state of the project (Patent Pending)23Bug – The Only Perfect Being

34. 24Bug – The Only Perfect BeingMost bugs are because imperfect requirements are imperfectly translated into imperfect design which is imperfectly translated into imperfect code

35. 25Whole Is More Than The Sum Of Parts

36. 26Whole Is More Than The Sum Of PartsAn integrated environment where…

37. 27Whole Is More Than The Sum Of PartsAn integrated environment where…

38. 28Integrated EnvironmentRequirementsVisual Prioritized Self-checking Testable ConstrainedDesign – Mapped to RequirementTests – Mapped to Requirements/Design/CodeCode – Mapped to Requirements/Design

39. 29Regression Test Selection Tool