IT Professionals

SERVICE BREAKDOWN
Business Hierarchy

• Client (Requirement)
• Business Analyst (Solvation Techniques)
• Developer (Analyse &Design)
• Tester (Validation & Verification)
Service Hierarchy

• Manager (Planning & Approval)

• Team Lead (Method & Improvising)
• Analyst (Analyse & Implement)
• Member (Design, Verify & Validate)
Software Testing
METHODS & IMPLEMENTATION
Types of Software Testing

• Functional Testing
• Non-Functional Testing (Performance Testing)
• Maintenance (Regression and Maintenance)
Methods of Software Testing

• Functional Testing
•Unit Testing (Smoke & Sanity)
•Integration Testing
•System Testing
•UAT ( User Acceptance Testing)
• Non-Functional Testing
•Performance Testing
•Load Testing
•Volume Testing
•Scalability
•Usability
• Maintenance (Regression and Maintenance)
Importance of Software Testing

• Bloomberg terminal in London crashed due to software glitch affected more than 300,000 traders on
financial markets.
• Nissan cars have to recall over 1 million cars from the market due to software failure in the airbag sensory
detectors.
• Starbucks was forced to close about 60 percent of stores in the U.S and Canada due to software failure in
its POS system. At one point store served coffee for free as they unable to process the transaction.
• Amazon’s third party retailers saw their product price is reduced to 1p due to a software glitch. They were
left with heavy losses.
• Vulnerability in Window 10. This bug enables users to escape from security sandboxes through a flaw in the
win32k system.
• Fighter plane F-35 fell victim to a software bug, making it unable to detect targets correctly.
• China Airlines Airbus A300 crashed due to a software bug killing 264 Innocent live
• Canada's Therac-25 radiation therapy machine malfunctioned due to software bug and delivered lethal
radiation doses to patients, leaving 3 people dead and critically injuring 3 others.
• A software bug caused the failure of a $1.2 billion military satellite launch, the costliest accident in history
• In may of 1996, a software bug caused the bank accounts of 823 customers of a major U.S. bank to be
credited with 920 million US dollars.
7 Principles of Testing

• Testing shows presence of defects

• Exhaustive testing is impossible
• Early Testing
• Defect Clustering
• Pesticide Paradox (test cases need to be regularly reviewed & revised)
• Testing is context dependent
• Absence of errors - fallacy
Software Engineering Terms

• SDLC
-sequence of activities carried out by Developers
to design and develop high-quality software.
• STLC
-series of activities carried out by Testers to test
software product.
Software Development Life Cycle

• Requirement Gathering
• Design
• Build
• Test
• Deployment
• Maintenance
Software Testing Life Cycle

• Requirement Analysis
• Test Planning
• Test case development
• Environment Setup
• Test Execution
• Test Cycle Closure
Test Plan

• Methods/Approaches
• Scopes and Out of Scopes Items
• Roles and Responsibilities
• Pre-requisites (Data Setup/Backend Check)
• Testing environment
• Risk and Mitigation Plans
Myths & Facts of Manual Testing

 Anyone can do manual testing

Testing requires many skill sets
 Testing ensures 100% Defect free product
Testing attempts to find as many defects as possible. Identifying all
possible defects is impossible.
 Automated testing is more powerful than manual testing
100% test automation cannot be done. Manual Testing is also essential.
 Testing is easy
Testing can be extremely challenging. Testing an application for possible
use cases with minimum test cases requires high analytical skills.
KEY DIFFERENCE Automation & Manual Testing

Manual Testing is done manually by QA analyst Automation Testing is done with the use of
(Human) script, code and automation tools (computer)
by a tester.

Manual Testing process is not accurate Automation process is reliable because it is

because of the possibilities of human errors code and script based.

Manual Testing is a time-consuming process. Automation Testing is very fast.

Manual Testing is possible without Automation Testing is not possible without
programming knowledge programming knowledge.

Manual Testing allows random Testing Automation Testing doesn’t allow random
Testing.
Defect/Bug Life Cycle

• New
• Assigned
• Open (Duplicate/Rejected/Deferred/Not a bug)
• Fixed
• Pending Retest
• Retest
Regression Test Selection

• Test cases which have frequent defects

• Functionalities which are more visible to the users
• Test cases which verify core features of the product
• Test cases of Functionalities which has undergone more and
recent changes
• All Integration Test Cases
• All Complex Test Cases
• Boundary value test cases
• A sample of Successful test cases
• A sample of Failure test cases
Testing Tools

• Test Management Tool

• Automated Testing Tools
• Cross-browser Testing Tools
• Load Testing Tools
• Defect Tracking Tools
• Mobile Testing Tools
• API Testing Tools
• Security Testing Tools
• CSS Validator Tool
Tools to Automate Manual Testing

• Selenium
• QTP
• Jmeter
• Loadrunner
• TestLink
• Quality Center(ALM)
Test Documentation

• Test Policy
• Test Strategy
• Test Plan
• Requirements Traceability Matrix
• Test Scenario
• Test Case
• Test Data
• Defect Report
• Test Summary Report
 Skills required to become a Software Tester

Verbal &
Passion Communication
skills

Technical Skills
Attitude

Good
Analytical Skills Software Productivity
Tester
Career Path Tester

• QA Analyst (Fresher)
• Sr. QA Analyst (2-3 years' experience)
• QA Team Coordinator (5-6 years' experience)
• Test Manager (8-11 years' experience)
• Senior Test Manager (14+ experience)