Testing Overview
and its history
Overview:
A primary purpose of testing is
to detect software failures so that defects may be discovered and corrected.
Testing cannot establish that a product functions properly under all conditions
but can only establish that it does not function properly under specific
conditions. The scope of software testing often includes examination of code as
well as execution of that code in various environments and conditions as well
as examining the aspects of code: does it do what it is supposed to do and do
what it needs to do. In the current culture of software development, a testing
organization may be separate from the development team. There are various roles
for testing team members. Information derived from software testing may be used
to correct the process by which software is developed.
Every software product has a
target audience. For example, the audience for video game software is
completely different from banking software. Therefore, when an organization
develops or otherwise invests in a software product, it can assess whether the
software product will be acceptable to its end users, its target audience, its
purchasers and other stakeholders. Software
testing is the process
of attempting to make this assessment.
History:
During the Years 1970-1980
software developers are used to do design, coding and testing the software and
at that time there is very less demand for the software or software projects.
But after the year 1980 there was huge demand for the software projects in the
market. At the time customer’s expectation was more and it become difficult to
provide quality or defect free software by the developer alone. So to provide
quality software or to satisfy the customer QUALITY and PRODUCTIVITY came into
picture. This was the time testing born. And testing and development separated.
Need of Testing
About testing
What: Identifying
the defects is called testing
Why: To find the
defects
To provide good quality Software
To improve the business
To satisfy the customer and their
requirements
When: In SDLC,
depending upon which model you are using for your project.
Who: By Test
Engineer, By Developers, By Customers and by end-users (the one who is using
the software)
How: It will be
describe in test plan
