Introduction to Software Testing. Software Development Life Cycle презентация

Agenda
Testing / Quality Control / Quality Assurance
Verification and validation
Software Project Team Roles
Software Development Life Cycle
Software Testing Life Cycle
Testing Principles

Software Testing
Software Testing -
a method to check
whether the actual software product matches expected requirements
and to ensure that software product is defect free.

What are the benefits of Software Testing?
Cost-Effective
Security
Product Quality
Customer Satisfaction

Testing / Quality Control / Quality Assurance

Testing / Quality Control Example
The task is to understand whether a detail is ready for release?
We should make a conclusion: is a detail ready for release?

Testing / Quality Control / Quality Assurance
Testing - the process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of a component or system and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
Quality control (QC) – a set of activities designed to evaluate the quality of a component or system.
Quality assurance (QA) - activities focused on providing confidence that quality requirements will be fulfilled.

Testing / Quality Control / Quality Assurance

Verification/Validation
Verification is testing that your product meets the specifications / requirements you have written. "Did I build what I said I would?".
Validation tests how well you addressed the business needs that caused you to write those requirements. It is also sometimes called acceptance or business testing. "Did I build what I need?"

Verification/Validation (Example)
When you order blueberry pancakes, what do you expect to see?
How do you determine that you have received what you ordered?

Verification/Validation (Example)
Does the food look like what pancakes typically appear to be?
Are the blueberries to be seen?
Do they smell right?
This is verification: all when you are yet to eat but are checking on a few things by reviewing the subject.
When you need to be sure about whether the food is as you expected: You will have to eat it.
Validation is when you eat the product to see if it is right.

Verification/Validation

Software Project Team Roles
QA Engineer
Business Analyst (BA)
Manager:
Product Manager
Delivery Manager
Project Manager

Software Project Team Roles
Developer:
Architect
Back End
Front End
DevOps
Data Specialist
UX/Designer

Software Development Life Cycle

2. Design
Defining system architecture (System Architecture documents)
Preparation of system and software design (Functional Design documents, Technical design documents)
Main Roles:
Architect/Developer
DevOps
Designer

3. Implementation
Writing code using the chosen programming language and according to the requirements and the design discussed in previous phases.
Main Roles:
Developer
Data Specialist

4. Testing
Verifying whether the application behaves as expected and according to what was documented in the requirements analysis phase.
Find defects within the system.
Main Roles:
QA

5. Deployment
Release the final version of software to the customer for their use.
Main Roles:
DevOps/Developer
Product Manager

6. Maintenance
User issues fixing
Upgrade - Upgrading the application to the newer versions of the Software
Enhancement - Adding some new features into the existing software
Main Roles:
Support Specialist
Developer
QA

STLC

Testing Principles
Testing shows presence of defects
Exhaustive testing is impossible
Early testing
Defect clustering
Pesticide paradox
Testing is context dependent
Absence of errors fallacy