Testing. General overview. Software testing презентация

Agenda
Testing: What?
Testing: Why?
Principles of Testing
Software Quality
Verification and Validation
Cost of the bug
Tester’s skill set
Course overview

Testing: What?
Testing – executing program or application and comparing actual behavior of the application against expected
Do you agree on this definition?
How would you define testing goal?

Software Testing – is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.
We are:
Clarifying what is expected
Detecting blind spots
Questioning things
Organizing and prioritizing
Analyzing risks
Assessing quality
Testing: What?
…and that’s so much more than just
“checking against expected”!

Software Testing is a separate complex discipline and profession
It does require theoretical knowledge along with practical skills and common sense
You should realize:
What’s special about it:
Testing varies a lot depending on the context
There is no single agreed approach that fits everything
Testing: What?

Testing: Why?
To prevent defects
Finding defects and errors that were made during the development phases
Ensure that the application should not result into any failures
Gaining confidence in and providing information about the level of quality
Check that the end result meets the business and user requirements
Makes sure of the Customer’s reliability and their satisfaction in the application
Provide the facilities to the customers
Effective performance of software application or product
It’s required to stay in the business
Testing goals and objectives:

Principles of Testing

Software Quality
Good design – looks and style
Good functionality – it does the job well
Reliable – acceptable level of breakdowns or failure
Consistency
Durable – lasts as long as it should
Good after sales service
Value for money
Key aspects of quality for the customer include:
Quality is the degree to which a system, component, or process meets customer or user needs or expectations

Verification
It makes sure that the product is designed to deliver all functionality to the customer;
Verification is done at the starting of the development process;
It includes reviews and meetings, walkthroughs, inspection, etc. to evaluate documents, plans, code, requirements and specifications;
Demonstration of consistency, completeness, and correctness of the software at each stage and between each stage of the development life cycle;
It is a Low level activity;

Validation
Performed after a work product is produced against established criteria ensuring that the product integrates correctly into the environment;
Determination of correctness of the final software product by a development project with respect to the user needs and requirements;
It is a High level activity;
Determining if the system complies with the requirements and performs functions for which it is intended and meets the organization’s goals and user needs;
Validation is done at the end of the development process and takes place after verifications are completed;

Validation: Am I building the right product?
Verification: Am I building the product right?
Verification vs Validation

Cost of the Bug
Relative cost factor to find and fix defects at each phase of the SDLC

Ariane 5

Radiation Therapy

Improve technical Skills
Know the Application and Industry
Be Hyper-sensitivity to Little Things
Be Organized and Tolerant to chaos
Improve people skills
Keep Skeptical, Curious and Artful
Be Honest and Firm
+ Diverse Testing Toolset
To become a great Tester…
You should:

Required Junior QC skills

It’s a long way to go…

Very nice step to start with! ☺
LQAS

Course Program

Each subject includes:
Workshop
Individual Homework assignment
Applying skills on our Test Project
Rules & Advices
Advices:
Take it seriously. But also enjoy it! ☺
Play your role
Be Pro-active, Question things all the time!
Be Attentive
Use this opportunity to get maximum for your own development!