Bug debug keynote - Present problems and future solutions
Upcoming SlideShare
Loading in...5
×
 

Bug debug keynote - Present problems and future solutions

on

  • 2,030 views

 

Statistics

Views

Total Views
2,030
Views on SlideShare
2,030
Embed Views
0

Actions

Likes
0
Downloads
78
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Bug debug keynote - Present problems and future solutions Bug debug keynote - Present problems and future solutions Presentation Transcript

  • 1
    Software Testing – Present Problems and Future Solutions
    Vipul Kocher
  • 2
    Science Fiction – Fiction today, Reality tomorrow
    Arthur C. Clark Geosynchronous satellites (1945) – Actual satellites (1963)
    Cloning - Dolly
    Jules Verne’s “Twenty Thousand leagues under the sea” (1869) – Simon Lake built “Argonaut” first submarine to operate in the open seas (1897)
  • 3
    What About These?
    Androids TimeTeleportation
    What about ? travel?
    ?
    How about self testing code?
    May that never become a reality as long as I live…
  • 4
    assumptions
  • 5
    Assumptions
    • All future solutions are based on today’s technologies
    • Disruptiveinnovationslike new class of operating systems, development paradigms, languages may significantly alter the landscapes
  • 6
    Assumptions
    I have a few ideas on
    • new class of Operating Systems
    • new class of programming languages and paradigms to support that operating system
    • ultimately supported by new class of hardware
    I have no clue about it !
  • 7
    problems in testing
  • 8
    Problems in Testing
    Are there problemsin testing?
    We all seem to be doing fine!
    Probably the biggest problem in testing is
    -“we do not have a problem”
  • 9
    Problems in Testing
    Why 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
  • 10
    challenges in testing
  • 11
    Challenges in Testing
    • What does testing mean for different stakeholders?
    • Have we tested enough?
    • How much time do I need to test it?
    • How many test cases should I write?
    • Oracle problem
    • How do I choose right set of regression tests?
    • How do I get developers to do better testing?
    • Do I need coding skills? What will I do with those?
    • How do I teaching testing to my testers?
  • 12
    What does testing mean for different stakeholders
  • 13
    What does testing mean for different stakeholders?
    Let us face it
    Nobody wants testing…
  • 14
    What does testing mean for different stakeholders?
    If one assumes that “testing is necessary” one is likely to try to improve the way testing gets done
    If one believes that testing is unnecessary then one is more likely to find ways to minimize or eliminate testing
    Mindset Matters !
  • 15
    testing world’s
    biggest problem
  • 16
    Testing World’s biggest problem
    • Where is the innovationin testing?
    • Innovation as in Breakthrough Innovation?
  • 17
    Testing World’s biggest problem
    Can you name three breakthrough innovations in testing? At least one?
    Where does the future of testing lie?
  • 18
    HITE
    E
    H
    I
    T
    Have I Tested Enough
    Do you have a bulletproof answer?
  • 19
    HITE
    First define “ENOUGH” –
    • Today
    - No catastrophic or critical or major failure for users
    • Tomorrow - ?
  • 20
    HITE
    • Integrated software status monitor- Explained later (Patent Pending)
    • New software technology- Self monitoring (Patent Pending), Self healing systems
    • Software testing as a distributed, automated service - you pay software companies to install software on your system and test it (Patent Pending)
  • 21
    How much time do I
    need to test it
  • 22
    How much time do I need to test it
    What 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?
    • Historical Data? Rule of thumb? Gut feel?
    Are these accurate? What about
    • Different 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)
    • Collection and analysis of data in automated manner and predictions based on current state of the project (Patent Pending)
  • 23
    Bug – The Only
    Perfect Being
  • 24
    Bug – The Only Perfect Being
    Most bugs are because imperfect requirements are imperfectly translated into imperfect design which is imperfectly translated into imperfect code
  • 25
    Whole Is More Than The Sum Of Parts
  • 26
    Whole Is More Than The Sum Of Parts
    An integrated environment where…
  • 27
    Whole Is More Than The Sum Of Parts
    An integrated environment where…
  • 28
    Integrated Environment
    Requirements
    Visual
    Prioritized
    Self-checking
    Testable
    Constrained
    Design – Mapped to Requirement
    Tests – Mapped to Requirements/Design/Code
    Code – Mapped to Requirements/Design
  • 29
    Regression Test Selection Tool
  • 30
    Tool-Chain
  • 31
    User Messages and API based test cases
  • 32
    Coverage & Data – Integral Part of Tool-Chain
    Customer care – database, emails, blogs
    Internet security advisories
    Standard
    Conformance
    Defect database, data-mining for bug-taxonomy
    Data from application monitoring in production
  • 33
    New format for writing test cases: visual format
  • 34
    An example of Visual format (http://www.exampler.com/software.html)
  • 35
    Ability to replay code
    Crash
  • 36
    Testing as a Framework
  • 37
  • 38
    Far Future – Where Testing?
    • Tool driven
    • Integral part of development
    • Better ways to tie all development artifacts together
    • Integration with various sources of information
    • Better analysis and action
  • 39
    Q & A
    Feel free to contact – vipul@puretesting.com