Scribd
Upload
23 views11 pages

ST U1L2 (Evolution of Software Testing)

Uploaded by

bright.keswani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
23 views11 pages

ST U1L2 (Evolution of Software Testing)

Uploaded by

bright.keswani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 11

BCECCE6104 (Software Testing)

UNIT - I
Unit Unit Details

1. Testing Methodology

● Introduction to Effective Software Testing


● Evolution of Software Testing, Software Testing Myths
● Goals of Software Testing
● Psychology for Software Testing
● Software Testing Definitions
● Model for Software Testing
● Role of tester- testing as a process
● Overview of Testing maturity model
● Defects -Hypothesis and tests
Evolution of Software Testing
and
Software Testing Myths
Evolution of Software
Testing
Early Days: Ad hoc and Manual Testing
• Testing was informal and focused mainly on debugging.
• Developers manually executed tests without formal planning or
documentation.

1970s–1980s: Emergence of Structured Testing


• Introduction of methodologies like white-box and black-box testing.
• Test plans and documentation became more organized.
• Focus shifted from defect fixing to systematic verification.
1990s: Test-Driven Development (TDD) and Automation
• Adoption of Test-Driven Development, writing test cases before coding.
• Rise of automation tools to handle repetitive and regression testing.
• Object-oriented programming added complexity, requiring new testing
techniques.

2000s: Agile Testing and Continuous Integration


• Integration of testing into iterative Agile methodologies.
• Emphasis on collaboration between developers and testers.
• Exploratory testing gained importance alongside structured methods.
• Continuous testing enabled faster feedback and adaptation.
2010s: DevOps and CI/CD Integration
• Testing became a key component of DevOps pipelines.
• Continuous Integration/Continuous Delivery (CI/CD) automated the
quality checks.
• Techniques like behavior-driven development (BDD) promoted
collaboration.

Present Day: AI-Driven and Intelligent Testing


• Use of AI and machine learning for predictive analytics and intelligent
test automation.
• Shift to testing user experience, security, and performance in addition
to functionality.
• Self-healing tests and tools for complex, dynamic systems.
So, software testing has evolved from a reactive, manual process to a
proactive, automated, and intelligent discipline. This evolution
underscores the growing importance of testing in delivering high-quality
software that meets the demands of an increasingly digital world.
Software Testing Myths
• Software testing, despite being a crucial part of the software
development lifecycle, is often surrounded by myths and
misconceptions.
• These myths can lead to misunderstandings about its purpose,
execution, and importance, potentially undermining the quality of the
software.
Myth-1: Testing is only about finding bugs.
Reality: Testing ensures software reliability, validates requirements, and
enhances user satisfaction beyond just identifying defects.

Myth-2: Testing guarantees a bug-free product.


Reality: While testing minimizes critical defects,
achieving absolute perfection is unrealistic due to
infinite input combinations and scenarios.

Myth-3: Testing should start after development completed.


Reality: Modern practices like Agile and DevOps emphasize early and
continuous testing to catch issues early and integrate testing throughout
development.
Myth-4: Skilled developers make testing unnecessary.
Reality: Even expert developers can overlook errors. Testing acts as an
independent evaluation to ensure the software meets user needs.

Myth-5: Automated testing can replace manual


testing.
Reality: Automation is great for repetitive tasks, but
manual testing remains essential for exploratory and
usability testing that require human judgment.

Myth - 6: Testing is expensive and time-consuming with little value.


Reality: Effective testing reduces costs by catching defects early and prevents
expensive fixes or reputational damage after release.
RECOMMENDED STUDY MATERIAL

S. No Text Books: Author Edition Publication

1. Software Testing-Principle and Practices Naresh Chauhan 3rd Oxford

2. Fundamentals of Software Engineering, RajibMall PHI 2018

Reference Book

1. The Art of Software Testing, 3rd Edition by Glenford J. Myers, Corey Sandler, Tom Badgett.

2. Software Testing, 2nd Edition by Ron Patton

Online Resources

1. https://www.javatpoint.com/software-testing-tutorial
2. https://www.guru99.com/software-testing.html

You might also like