This document outlines an introduction to software testing training course. The course agenda covers topics like software testing concepts, the software development life cycle, quality standards, testing methods, tools and automation. It defines key terms like quality assurance, quality control, verification and validation. The course modules will cover introductions to QA and testing, SDLC, manual testing, requirements, configuration management, testing strategy, defect lifecycles, and testing tools and automation. It also discusses whether testing is a technical role and the differences between projects and products.
2. Page 2Classification: Restricted
Agenda
• Course Overview
• Introduction to Software Testing
• Is Testing a Technical role
• Project And Product
• Quality Assurance Vs Quality Control
• QC VS QA
• Verification and Validation
3. Page 3Classification: Restricted
• Module 1 – Introduction to QA – Software Testing
• Module 2 – Software Development Life Cycle(SDLC) and Quality Standard
• Module 3 – Testing Concepts and Manual testing
• Module 4 – Requirements, Configuration Management, Strategy and Defect
life Cycle
• Module 5 – Testing Tools and Automation
Software Quality Testing
4. Page 4Classification: Restricted
• What is Testing? What is QA? Are they the same or different?
• Is Testing a Technical Role? Do we need technical knowledge?
• Projects And Products
• Quality Analyst and Quality Control
• Verification and Validation
• Defect/Bugs in Software Testing
• Quality Team Roles and Responsibilities
• Career options available for a Test Engineer
• Testing Market and Opportunities
• Class Assignment
Module 1- Introduction to QA-Software Testing
5. Page 5Classification: Restricted
Day 1- Introduction to Software Testing
Software Testing
Software testing is a planned process that is used to identify the
correctness, completeness, security and quality of software.
Testing is generally done to demonstrate that the software is doing
what it is supposed to do as well as the software is not doing what it is
not supposed to do.
Quality Assurance
QA is planned and systematic way to evaluate quality of process used to
produce a quality product. The goal of a QA is to provide assurance that a
product is meeting customer’s quality expectations.
6. Page 6Classification: Restricted
Is Testing a Technical role
Is Testing a Technical Role? Do we need technical knowledge?
Testing plays crucial role in IT industries but does not required any technical
knowledge when comes to Manual Testing . The main focus is to plan and
perform Functional Testing from a user’s perspective.
A tester needs to have excellent Communications skills, Technical skills,
Leadership qualities and Analytical / Judgment skills. He or she must
develop out of the box and critical thinking, be creative and strive for
excellence. Technical skills would need to be supplemented with good
domain knowledge. This includes an ability to write code, good
understanding of systems and application architecture, and knowledge of
databases.
7. Page 7Classification: Restricted
Project And Product
Project: Project is developed based on the customer requirements and his
usage only.
Product: Product is developed based on the company specifications a use
multiple costumers
8. Page 8Classification: Restricted
Quality Assurance Vs Quality Control
Quality Assurance
The function of software quality that assures that the standards, processes,
and procedures are appropriate for the project and are correctly
implemented.
Quality Control
QC is a set of activities for ensuring quality in products. The goal of QC is to
identify defects after a product is developed and before it's released.
10. Page 10Classification: Restricted
Verification and Validation
Verification
Verification is a static practice of verifying documents, design, code and
program. It does not involve executing the code. It is human
based checking of documents and files. Verification uses methods like
inspections, reviews, walkthroughs, and Desk-checking etc.
Validation
Validation is a dynamic mechanism of validating and testing the actual
product. It always involves executing the code. It is computer based
execution of program. Validation uses methods like black
box (functional) testing, gray box testing, and white box (structural) testing
etc.