• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Software Testing Does your software product perform as it is ...
 

Software Testing Does your software product perform as it is ...

on

  • 368 views

 

Statistics

Views

Total Views
368
Views on SlideShare
368
Embed Views
0

Actions

Likes
0
Downloads
5
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

    Software Testing Does your software product perform as it is ... Software Testing Does your software product perform as it is ... Presentation Transcript

    • Software Testing
      • Does your software product perform as it is intended to perform?
      • Presented by:
      • Andy Bouts
      • John Kinuthia
    • Content
      • Introduction
      • Background on software testing
      • Modern views of software testing
      • Key Terminology
      • Categories of software testing
      • OO software testing environment
      • Lessons Learned; Object oriented testing
      • Conclusion
    • What is Software Testing?
      • Process of examining a software product or part of a software product to determine whether a software performs as it is expected to perform
      • Software testing is a part of quality assurance
      • Quality assurance: takes into account all business processes and not just testing
    • Testing outcomes
      • Desired results are / are not achieved
      • Non – desired results are / are not achieved
      • Users accept / do not accept product
    • History of Software Testing
      • There are four distinct periods of time that mark the development of software testing during the twentieth century.
      • During these periods, software testing has changed from its earliest days of continuously debugging to the more proactive approaches of today.
    • Four Periods of Development
      • 1957-1978: Engineers distinguish between testing and debugging software. This is the first time they were able to prove that a software system can meet requirements.
      • 1979-1982: Engineers began trying to break the system to find errors, instead of just debugging the known errors.
    • Four Periods of Development
      • 1983-1987: Engineers began offering ‘observational periods’ on software, today these periods as called beta programs.
      • 1988-Present: As software projects are more closely managed in terms of financials, risk, and timing, the focus has shifted toward detecting errors as soon as possible. This is because early detection leads to better products which are often delivered on time and with less risk to manage.
    • Software Testing: Modern View
      • Software should be tested during different stages of system development life cycle.
      • Almost all software is developed using a type of iterative beta program where programmers, testers, developers, and users are encouraged to break the software or find software functionality that does not meet desired results.
      • It has been proven that it is cheaper to fix defects if detected early in development stages.
    • Key Terms: Black Box Testing
      • Black, White, or Grey Box Testing refers to the point of view taken while designing test cases and plans.
      • Black Box Testing (BBT) takes an external view of the test object.
      • BBT focuses on inputs and outputs of the system, user functionality of the system, and the higher level workings of the system.
      • BBT is often automated and is usually one of the final steps before software is released.
    • Key Terms: White Box Testing
      • White Box Testing (WBT) is focused on the internal aspects of the system.
      • WBT test cases and test plans are usually developed by programmers and engineers who understand and want to examine the inner workings of the system.
      • WBT is usually among the earliest tests performed in software development.
      • WBT can also be used to evaluate and fix system errors for software that is already in production.
    • Key Terms: Grey Box Testing
      • Grey Box Testing (GBT) is a hybrid of the black and white box testing.
      • GBT is usually focused around databases and connectivity.
      • GBT often requires the tester to populate a development database with sample data to evaluate the proper workings of the data store.
      • Testers for GBT are often proficient with SQL, XML, or other data centric languages / technologies.
    • Three Types of Testing
      • “Component testing tests the minimal software item that can be tested.” 1
      • “Component integration testing exposes defects in the interfaces and interaction between integrated components.” 2
      • “System testing tests an integrated system to verify that it meets its requirements.” 3
        • A team’s failed integration test…
        • 1,2,3: http://en.wikipedia.org/wiki/Software_testing
    • Acceptance Testing
      • “Acceptance testing - allows the end-user or customer to decide whether or not to accept the product.” 1
        • “ Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site.” 2
        • “ Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the company.” 3
        • 1,2,3: http://en.wikipedia.org/wiki/Software_testing
    • Regression Testing
      • Regression testing is often used to re-test functionality that has previously passed system or acceptance testing.
      • It is being re-tested because of changes to the software code to ensure that the system still works properly and that the changes have not introduced unintentional regression of previously achieved results.
      • A vendor’s failure to thoroughly regression test…
    • OO Testing Environment … Unique Challenges
      • In an Object Oriented (OO) programming environment, individual parts (objects) work together as a system.
      • An object has a set of attribute values that define a state of the object and the actions the object can do.
      • Because objects are the basic building blocks of a system, any change to their attribute values functionality, or accessibility may cause unintended changes downstream in the environment.
    • OO testing environment: So what’s the problem?
      • In the paper, Developing an Object-Oriented Software Testing and Maintenance Environment, the main problems seen during OO testing are 1 :
        • The understanding problem
        • Complex interdependency
        • Object state behavior testing problem
        • The tool support problem
        • 1: Article Citation
    • The Understanding Problem 1
      • It becomes difficult to decipher to process / data flow when encapsulation and information hiding are used.
      • Often multiple objects are used with multiple classes creating a system that can use an exponentially large number of object combinations.
        • 1,2: Article Citation
    • The Understanding Problem 1
      • Understanding the relationships between objects is important for a successful test.
      • “Although each of the member functions is very small (a total of 15 lines of code, or an average of 5 lines per member function), it took, on average, 0.95, 0.93, and 0.79 person-hours to prepare the test data, test driver, and test stub, respectively.” 2
        • 1,2: Article Citation
    • Complex Dependency Problem 1
      • Analysts and testers spend large amounts of time trying to understand classes in large OO program and determine if the classes depend on other classes.
      • “Without sufficient insight, a tester may not know where to start testing an OO library.” 2
        • 1,2: Article Citation
    • Complex Dependency Problem 1
      • “It is difficult to identify and test the effect of polymorphism and dynamic binding.” 2
      • “It is difficult to identify change impact in OO maintenance, since the impact may ripple throughout the OO program through the complex dependencies.” 3
        • 1,2,3: Article Citation
    • The State Behavior Testing Problem 1
      • What an object returns is very dependant on the state of the object when it is told to act.
      • It is erroneous to assume a product works fine by just testing individual operations without evaluating the object’s state.
      • Integration testing doesn’t solve this problem; it will just test that individual member functions are interfacing correctly.
        • 1: Article Citation
    • The Tool Support Problem 1
      • Conventional testing methods used by commercially available software may not necessarily deal with problems identified in object oriented testing.
      • It is better to have a formal specification language that will be used by a testing tool to derive test cases customized to meet software specifications.
        • 1: Article Citation
    • An OO Testing Situation
      • “Central to the environment is a mathematically defined test model, consisting of three types of diagrams:” 1
      • ORD: Object relation diagram - represents inheritance, aggregation, association 2
      • BBD: block branch diagram - represents the control structure of a member function and its interface to other member functions 3
      • OSD: Object state diagram - represents the state behavior of an object class 4
        • 1,2,3,4: Article Citation
    • Advantages of OO Test Model
      • It uses graphical models to explain the relationships between classes and objects.
      • It accelerates preparations by helping the tester / analyst work more efficient.
      • It assists with defining and analyzing OO testing specs.
      • “It facilitates the development of the various algorithms and capabilities for OOTM.” 1
        • 1: Article Citation
    • Software Testing as an Industry
      • Software testing has grown and is continuing to develop as an industry.
      • Larger companies have teams and / or departments that are solely focused on testing.
      • Often firms utilize automated testing tools to supplement human testing.
    • Testing Industry: Companies
      • http://www-306.ibm.com/software/rational/offerings/testing.html
      • http://www-128.ibm.com/developerworks/rational/kits/tester/?S_TACT=105AGX23&S_CMP=SWQ
      • IBM will provide consulting or testing packages.
    • Automated Test Software
      • http://www.surgient.com/solutions/devtest/?gclid=CL-P2f73sIgCFQ5_UAodB1er3g
      • http://www.seapine.com/products.html
      • Seapine offers a full suite of software development tools supporting the entire development life cycle.
    • Conclusions
      • Test early and test often
      • Integrate the application development and testing life cycle. You'll get better results and you won't have to mediate between two armed camps in your IT shop.
      • Formalize a testing methodology; you'll test everything the Same way and you'll get uniform results.
      • Develop a comprehensive test plan; it forms the basis for the vesting methodology.
      • Use both static and dynamic testing .
    • Conclusions
      • Define your expected results.
      • Understand the business reason behind the application. You'll write a better application and better testing scripts.
      • Review and inspect the work; it will lower costs.
      • Use multiple levels and types of testing (regression, systems, integration, load).
      • Don't let your programmers check their own work; they'll miss their own errors
    • Questions
      • Do you have any questions?
    •