• Embed Doc
  • Readcast
  • Collections
  • CommentGo Back
Download
 
TESTING CONCEPTS
Beginners Guide to Software Testing
ByM.Saravanan(Software Testing Engineer)
1
 
TESTING CONCEPTS
FOREWORD
Beginners Guide to Software Testing introduces a practical approach to testingsoftware. It bridges the gap between theoretical knowledge and real worldimplementation. This article helps you gain an insight to Software Testing -understand technical aspects and the processes followed in a real workingenvironment.
Who will benefit?Beginners:
For those of you who wish to mould your theoretical softwareengineering knowledge into practical approach to working in the real world.Those who wish to take up Software Testing as a profession.
Developers!
This is an era where you need to be an “All rounder”. It isadvantageous for developers to posses testing capabilities to test the applicationbefore hand. This will help reduce overhead on the testing team.
Already a Tester!
You can refresh all your testing basics and techniques and gearup for Certifications in Software Testing
An earnest suggestion:
No matter which profession you choose, it is advisable thatyou posses the following skills:● Good communication skills – oratory and writing● Fluency in English● Good Typing skillsBy the time you finish reading this article, you will be aware of all the techniques andprocesses that improves your efficiency, skills and confidence to jump start into thefield of Software Testing.
Beginners Guide To Software Testing
is our sincere effort to educate and createawareness among people, the growing importance of software quality. With theadvent of globalization and increase in market demand for software with good
2
 
TESTING CONCEPTS
quality, we see the need for all Software Engineers to know more about SoftwareTesting.We believe that this article helps serve our motto – “Adding Values to Lives AroundUs”.
A brief history of Software Engineering
Being a Software Test Professional, you must know a brief history of SoftwareEngineering. Software Testing comes into picture in every phase of SoftwareEngineering.The software industry has evolved through 4 eras, 50’s –60’s, mid 60’s –late 70’s,mid 70’s- mid 80’s, and mid 80’s-present. Each era has its own distinctivecharacteristics, but over the years the software’s have increased in size andcomplexity. Several problems are common to almost all of the eras and are discussedbelow.The Software Crisis dates back to the 1960’s when the primary reasons forthis situation were less than acceptable software engineering practices. In the earlystages of software there was a lot of interest in computers, a lot of code written butno established standards. Then in early 70’s a lot of computer programsStarted failing and people lost confidence and thus an industry crisis was declared.Various reasons leading to the crisis included:- Hardware advances outpacing the ability to build software for this hardware.- The ability to build in pace with the demands.- Increasing dependency on software’s- Struggle to build reliable and high quality software- Poor design and inadequate resources.This crisis though identified in the early years, exists to date and we haveexamples of software failures around the world. Software is basically considered afailure if the project is terminated because of costs or overrun schedules, if theproject has experienced overruns in excess of 50% of the original or if the softwareresults in client lawsuits. Some examples of failures include failure of Air trafficcontrol systems, failure of medical software, and failure in telecommunication
3
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
You must be to leave a comment.
Submit
Characters: ...