Basic history of software testing
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Basic history of software testing

on

  • 4,832 views

In order to create excellent software, an effective and efficient software testing process is needed. The purpose of this article is to take a look at software testing as we know it today.

In order to create excellent software, an effective and efficient software testing process is needed. The purpose of this article is to take a look at software testing as we know it today.

Statistics

Views

Total Views
4,832
Views on SlideShare
4,342
Embed Views
490

Actions

Likes
0
Downloads
66
Comments
0

3 Embeds 490

http://shortcourses.ca 269
http://www.shortcourses.ca 211
https://twitter.com 10

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

Basic history of software testing Presentation Transcript

  • 1. Basic History of Software Testing www.universalexams.com
  • 2. Introduction
    • Anyone who has worked with computers or software will attest to the wonders that technology can accomplish.
    • But for software companies, creating the actual software is only half the battle; devising the method of testing it is equally challenging.
    • And in order to create excellent software, an effective and efficient software testing process is needed.
    • The purpose of this presentation is to take a look at software testing as we know it today.
  • 3. Origins of Software Testing
    • The origins of software testing can actually be traced back to the fifties, when the primary method of testing anything was debugging.
    • In the late seventies, the approach evolved to one of destruction; basically, the testers would break down the code to find holes or gaps in it.
    • This method was effective but it was not until the advent of prevention oriented methodologies that we began to enjoy the benefits of more robust software applications.
  • 4. Origins of Software Testing (cont.)
    • In 1979, Glenford J. Myers correctly hypothesized that there must be a distinction between debugging, which means identifying and eliminating bugs in the software code, and actually testing the software in real world settings.
    • It was during this time that there was a distinct shift toward software testing as we know it today.
  • 5. Why Software Testing Matters
    • If you are reading this article on your computer, the Internet Browser you are using has gone through countless hours of testing to ensure the software is not only stable but secure as well.
      • There are many shady characters out there trying to exploit weaknesses in the code and the only barrier between us and chaos is effective software testing.
    • Similarly, the operating system you are currently using on your computer is a work of human ingenuity.
      • Envision having to draft a software program that not only can handle the ever changing needs of users, but can also manage hardware drivers and a host of other conflicting resources.
      • It’s no wonder programmers work as hard as they do!
  • 6. Why Software Testing Matters (cont.)
    • Every component of the system must act in harmony, and if the software is not coded correctly it will not only crash but could affect other programs within the same directory.
    • Thus, to conduct effective software testing you must build something that works seamlessly, and then to make things interesting you need to figure out ways to make it crash in order to correct the associated flaws.
    • Not an easy undertaking and surely not for the faint of heart.
  • 7. Why Software Testing Matters (cont.)
    • An important question to ask is who will be using this software.
    • Will it be a single end user or multiple users at the enterprise level or both?
    • The level of complexity in the coding will be dictated by the end user.
    • Will the software have a one-time release or will there be ongoing updates?
    • This and similar issues are worth considering when programmers are hashing out ideas.
  • 8. Conclusion
    • One certainty is that without sufficient testing any piece of software will eventually fail, leaving the user base unhappy and in search of another solution.
    • All companies want happy users, and thus effective software testing is of paramount importance to their future and bottom line.