Software testing course - Manual

FOUNDATION
SOFTWARE TESTING
Video 1

WHAT IS TESTING
Google says: “a procedure intended to establish
the quality, performance, or reliability of
something, especially before it is taken into
widespread use.”

“Software testing is a process of executing a
system or system component in order to find
bugs and errors.”
Or
“Software testing is process of Verification and
Validation (v&v), performed on Application
under Test (AUT) with an intention of finding
bugs and errors.”
SOFTWARE TESTING IS:

SOFTWARE TESTING LIFE CYCLE
STLC

“STLC stand for Software Testing Lifecycle. STLC is a
set of process which is executed in a systematic
manner to achieve the testing goal”
STLC

STLC PHASES:
TEST PLANNING
TEST DESIGNING
TEST ENVIRONMENT
TEST EXECUTION
BUG REPORTING &
MANAGMENT
RTM (REQUIREMENT
TRACEABILITY
MATRIX)
TEST REPORTING

PLANNING
● Test Objective
● Test Strategy
● Resources
● Schedules & timelines
● Risks
● Entry & Exit Criteria
TESTING PHASES

TESTING PHASES
DESIGNING
● Test Scenarios
● Test Cases
● Test scripts

ENVIRONMENT
● QA Environment
● Test Data
● Tools and Technologies or Software and
hardwares
TESTING PHASES

BUG MANAGEMENT
● How to raise a bug
● Bug components
● Bug lifecycle
TESTING PHASES

TEST REPORTING
● Test results
● Bug report
● Test coverage
● Lesson learnt
TESTING PHASES

TESTING IMPORTANCE
Testing is important, to make sure:
• All business requirements are implemented
• Functionalities are behaving as expected
• Application is secure enough
• Does not break under working circumstances
• Does not harm the business reputation
• Performs its functions within an acceptable time
• Works well on all supported OS, devices and screens
• To make sure that customer can trust and rely on your
product

A CLASSIC EXAMPLE
“NASA’s climate orbiter
was lost due to the two
agencies NASA and
Lockheed Martin used
two different
measurement units and
that was not tested or
was left during the
testing.”

KNOW THE DIFFERENCE
QA, QC & TESTING
Video 2

“A product’s degree of excellence is quality.
Quality can be judged by how product
matches with requirement and how
accurately and/or efficiently the work can be
done”
QUALITY

“QA is a systematic and scientific approach of
monitoring and improving the software
development process.”
It’s a verification activity and the idea behind this is to
prevent the errors occurring in software development
process.
QA

“QC is a validation activity where the quality
of the developed product is evaluated with a
benchmark or any competitive program’s set
standard to make sure that the software
quality is adhering the defined or expected
quality.”
QC

The difference:
QUALITY ASSURANCE QUALITY CONTROL
QA is a verification process QC is a validation activity
QA is process oriented QC is product oriented
QA prevents the defect QC finds the defect
It improves the development
process
It improves the developed
product quality
Requirement document, design
review and code reviews are
done as part of this
Product testing is done as part
of this activity
Performed without the program
execution
Performed by executing the
program

“Testing is a validation activity so it comes
under QC. Wherein the developed program is
executed with an intention of finding bugs”
TESTING

SOFTWARE DEVELOPMENT LIFE CYCLE
SDLC
Video 3

“SDLC stands for Software Development Life
Cycle. SDLC defines the standard phases
involved throughout the software
development.”
SDLC

SDLC PHASES
Deployment
Requirement Analysis
Project planning
Maintenance
Project Designing
Testing
Development

▶ Waterfall Model
▶ Spiral model
▶ Prototype Model
▶ Iterative and Incremental Model
▶ V -Model
▶ W-Model
▶ Agile Mode
SDLC MODELS

“Waterfall model is a sequential development model
where each phase of SDLC is executed one after
another in a linear way so its also called linear
sequential model”
Waterfall Model:
REQUIREMENT
DESIGN
DEVELOPMENT
TESTING
DEPLOYMENT
MAINTENANCE

“The spiral model is a risk-driven process model
generator for software projects. Based on the unique
risk patterns of a given project, the spiral model
guides a team to adopt elements of one or more
process models, such as incremental, waterfall, or
evolutionary prototyping.”
Spiral Model:

“In this model a software prototype will be created to
understand that whether it satisfies the stakeholder’s
requirements.”
Prototype Model:
Prototyping is used to allow the users evaluate
developer proposals and try them out before
implementation

“In incremental model the whole requirement is
divided into various builds. Multiple development
cycles uses waterfall model. Cycles are divided up
into smaller, more easily managed modules.”
Incremental Model:

“In V model of SDLC the real development phases
and testing plans goes side by side as It can be
interpreted as in a 'V’ shape”
V Model:
REQUIREMENT
ANALYSIS
UAT (USER ACCEPTANCE
TESTING)
HIGH LEVEL DESIGN SYSTEM TESTING
LOW LEVEL DESIGN
or SPECIFICATION
INTEGRATION
TESTING
CODING UNIT TESTING

“In V model of SDLC the real development phases
and testing plans goes side by side as It can be
interpreted as in a 'V’ shape”
W Model:
REQUIREMENT ANALYSIS UAT (USER ACCEPTANCE
TESTING)
HIGH LEVEL
DESIGN
SYSTEM TESTING
LOW LEVEL DESIGN or
SPECIFICATION
INTEGRATION TESTING
CODING UNIT TESTING
REQUIREMENT REVIEW
HLD Review
SPECIFICATION
Review
Code Review
DEPLOYMENT
BUILD
CODE MERGE

“Agile is a software development model that gives the
flexibility to develop, test and deploy the things
quickly and easily.”
or
“Agile is software development model that implements
the continuous iteration approach to develop and
deploy a product where requirement changes very
frequently”.
AGILE MODEL:

“A test plan is a document that describes that what
and how to achieve something in AUT (Application
Under Test).”
TEST PLANNING:
Making of a test plan is very first step in software
testing lifecycle and it defines the rule, covers the
scope, analyzes the available resources, timeline and
risks associated with the testing of a project.

Follow the below mentioned steps to make a good test
plan document:
▶ Analyze the business requirement
▶ Find the test objective
▶ Define a Test Strategy
▶ Analyze the risks (Tools, Resources and Time)
▶ Test Environment and Test Data preparation
▶ Define Entry & Exit Criteria
▶ Define a Traceability Matrix
▶ Schedule and Timeline
▶ Deliverable
TEST PLAN DOCUMENT:

▶ Understand the requirement by going through the
requirement document
▶ Note down and resolve your queries
▶ Get a product or document reviewed
ANALYZE BUSINESS
REQUIREMENT:

The objective of the testing is finding as many valid
defects as possible and ensure that the software
under test is bug free before release.
In this phase you need to find out the core motive of
your product. You should need to know
▶ Bug Free features
▶ Smooth performance
▶ No security threats
FIND TEST OBJECTIVE:

“Test strategy defines the software testing approach
to achieve the testing goal. Usually the test strategy
document is created by Test Manager and It says
what type of technique to follow and which module
(scope) to test” Test strategy can be defined that:
▶ How to get maximum requirements under testing
umbrella by putting minimal effort
▶ What sort of testing you need to perform
▶ What tools will be required
DEFINE TEST STRATEGY:

▶ Find out that do you have available tools required
for testing
▶ Find out that do you have required skills to test
▶ Find out if you have enough resources to complete
the task in the given time frame
▶ Find out that you have sufficient time to complete
the testing
ANALYZE THE RISKS:

“Test Environment is also called Test Bed setup, it
means laying down all the needed softwares or
hardwares required for a tester to execute the test
scripts.”
“In order to work on something or to process any
request a tester need some data which they can place
as an input and that’s called a test data”
TEST ENVIRONMENT & TEST
DATA PREPARATION:

“Entry criteria is the prerequisites that
must needs to be fulfilled before test team
can begin the testing.”
In most of the places smoke/sanity testing is defined
and the cases of smoke sanity must be passed as
condition of Entry criteria.
DEFINE ENTRY CRITERIA:

“Exit criteria are some conditions that must be
fulfilled by test team before they can conclude their
testing activities” like the test coverage should reach
100% of traceability matrix, all the test deliverable
are shared and many other things.
▶ Verify that all business requirements are covered
as part of testing
▶ No critical bugs are in open state
DEFINE EXIT CRITERIA:

The Requirement Traceability Matrix or RTM is a
document that maps the business requirement and
test cases to trace the coverage of testing at any given
point of time and to ensure that no requirement is
missed as part of the testing.
The main purpose of Requirement Traceability Matrix
is to see that all test cases are covered so that no
functionality should miss while testing.
DEFINE TRACEABILITY MATRIX:

DEFINE SCHEDULE& TIMELINE:
Planning Designing Execution
X Days Y Days Z Days

DEFINE DELIVERABLES:
Test deliverable are the documents, scenarios, test
cases, test scripts, test data, screenshots and bug
reports that is shared during or after the testing life
cycle.

TEST DESIGNING
TEST SCENARIOS, TEST CASES & TEST SCRIPTING
Video 5

TEST SCENARIOS:
Test scenario meaning finding out that ‘what to be
tested’ in any given requirement. This is to make
sure that end 2 end functionality is covered.
or
“Test scenarios are the high level classification of test
requirement grouped depending on the functionality
of a module”

TEST SCENARIO EXAMPLE:
Requirement: ‘Login the website, select and play your
favourite music’
Scenario 1: Test the login function
Scenario 2: Search for the music based on different
genres and play
Scenario 3: Create your music playlist
Scenario 4: Play the songs from your playlist

TEST CASE:
“ A test case, in software testing, is a set of conditions
under which a tester will determine whether an
application, software system or one of its features is
working as it was developed and expected to do.”

TEST CASE EXAMPLE:
Let’s pick 2 scenario from scenario example:
Scenario 1: Test the login function
TC 1: Test the login function with valid credentials
TC 2: Test the login function with invalid credentials and verify the
result
TC 3: Check and validate the error msgs for login errors
Scenario 2: Search for the music based on different
genres and play
TC1: Search for specific genre songs and play them
TC2: Check the player functionalities (play, pause, stop, forward, ..)
TC3: Check that the songs can be added in your playlist

TEST SCRIPTING
“In order to execute test cases a detailed procedure
needs to be written where the writer will mention all
the steps to be performed and what should be the
expected result for each activity”

BLACK BOX TECHNIQUES
BVA, ECP, DECISION TABLE & USE CASE TESTING
Video 7

TECHNIQUES
“Test Case designing technique is needed to get the
maximum coverage by using an optimal number of
test cases.
▶ Equivalence Class Partitioning
▶ Boundary Value Analysis
▶ Decision Table
▶ Use Case Testing

Equivalence Class Partitioning
“ECP is a testing technique that divides the input test
data into partitions of equivalent classes and from
each class minimum one data must be tested at least
once.”

BVA Example
Scenario: Assume that there is an input field for age
and it accepts the values from 1-100. So, if we follow
the ECP concept then:
Valid Class
values from
1 -100
Invalid Class
values below 1
(0- anything)
Invalid Class
values above 100
(101- anything)
Class A : Any value from valid input data domain : 1-100
Class B : Any value which is lower than lowest : 0,-1,-2..
Class C : Any value which is higher than Highest : 0,-1,-2..
Class D: Any alphanumeric : A1, B1, C1
Class E: Any decimal values: 1.1,1.2,1.3

Boundary Value Analysis
“More application errors occur at the boundaries of
input domain. ‘Boundary value analysis’ testing
technique is used to identify errors at boundaries
instead of finding errors in center of input domain.”

BVA Example
Scenario: Assume that there is an input field for age
and it accepts the values from 1-100. So, if we follow
the ECP concept then:
Valid Boundary
values 1 & 100
one lower than
lowest = 0
one higher than
highest = 101
Boundary Value: 1 & 100
Invalid values for negative test cases: 0 & 101

Decision Table
“Decision table technique is used in complex
business scenarios where the input data will be
determined based on some conditions.”
Ex:
Conditions 1 2 2
Cash Yes No No
Coupon N/A Yes No
Actions
Order Placed Yes Yes No

USE CASE Testing
▶ Use Cases capture the interactions between
'actors' and the 'system'.
▶ A use case is a description of a particular use of
the system by an actor. Each use case describes
the interactions the actor has with the system in
order to achieve a specific task.

SOFTWARE TESTING TYPES
TESTING TREE
Video 6

WHITE BOX, BLACK BOX &
GRAY BOX TESTING
Video 8

WHITE BOX TESTING or
Structural Testing or Glass Box
Testing
▶ Testing the code and internal structure comes
under white box testing.
▶ Code’s internal structure, design and
implementation is tested as part of white box
testing.
▶ It is also known as ‘glass box testing’ or ‘Open
box testing’ or ‘Structural Testing’.

WHITE BOX TESTING TYPE
UNIT TESTING:
Once the developer develops their piece of segment,
each individual component is tested independently in
this testing for their expected outcomes.
INTEGRATION TESTING:
When two independent units of codes merged then
checking that whether they functioning together is
called integration testing.

WHITE BOX TESTING
TECHNIQUES- CODE COVERAGE
STATEMENT COVERAGE
This technique requires every possible statement in
the code to be tested at least once during the testing
process
BRANCH COVERAGE
This technique checks every possible path like if-else
and other conditional loops of a software application

WHITE BOX TESTING IS
PERFORMED TO FIND
CODE COVERAGE
▶ Poorly structured codes
▶ Output of the code
▶ Conditional loops
▶ Internal security holes
▶ Cover branch and statement

BLACK BOX TESTING
“ Black Box Testing is the testing method where
Functional and nonfunctional aspects of the
application is tested without looking into the code.”
Also known as Behavioural Testing or close box
testing.

Black Box Test is performed to
check
▶ Missing on incorrect features
▶ Performance errors
▶ Security errors
▶ Database connection
▶ APIs
▶ ...

BLACK BOX TESTING TYPES
▶ FUNCTIONAL TEST
◦ Smoke/Sanity
◦ Feature testing
◦ Regression testing
◦ System Testing
◦ UAT
▶ NONFUNCTIONAL TEST
◦ Performance (Load/stress/soak)
◦ Compatibility testing
◦ Usability testing
◦ GUI testing

GARY BOX TESTING
“Gray Box Testing is a combination of White box
testing and black box testing. The idea is to find the :
Improper structure and/or
Improper usage of application”
▶ It is based on functional specification, UML
Diagrams, Database Diagrams or architectural
view
▶ Grey-box tester handles can design complex test
scenario more intelligently

FUNCTIONAL TESTING
TYPES EXPLAINED on next level
Video 9

UNIT TESTING
Once the developer develops their piece of segment,
each individual component is tested independently in
this testing for their expected outcomes.

INTEGRATION TESTING
When two independent units of codes merged then
checking that whether they functioning together is
called integration testing.

Integration Testing STUBS & DRIVERS
Stubs and drivers are the dummy piece of code called
in to create an integrated environment where some
work is not completed yet or not available for testing.
▶ Stubs are used during top down integration
approach
▶ Drivers are used In bottom up integration
approach

SMOKE/SANITY TESTING
▶ Smoke/sanity testing is also called Build
verification testing or confidence testing
▶ The motive of this testing is to ensure that the
major & critical functions are working as expected
▶ So that the test team can get enough level of
confidence about the application’s stability and
can execute the other testings.

SMOKE/SANITY TESTING Example:
Smoke testing is collection of test cases that covers
the most crucial functions of AUT (Application Under
Test).
An example of smoke/sanity test cases for a website:
▶ URL is accessible
▶ User is able to login
▶ The payment is being successful

SMOKE/SANITY TESTING Difference:

Functionality, Regression
Retesting

Functionality TESTING
“For any new release of the product, testing the
added or modified requirement is called functional
testing.”
Functional testing is done to check that all the
business functionalities are working ok as expected
and it will fulfill the end user’s requirement.

Regression TESTING
When a new functions is added or an existing
application function is modified then checking the
existing features is called regression testing as the
newly added/modified feature may create some side
effects for other features.
▶ This testing is done after every release
▶ Regression test suite shall be updated after every
new release.

Functionality & Regression Difference

Retesting
Once a bug is fixed then checking the same
functionality again to ensure that the bug fix is ok is
called retesting. This testing is done to ensure that
bug fix is working ok and based on that the bug
status will be updated as fixed or reopened.

SYSTEM TESTING
▶ System testing is testing the whole system in
integrated environment with all necessary
software and hardwares.
▶ Usually performed in E2E (End 2 End)
environment
In complex business scenarios one system work with
collaboration of so many other systems, so testing
your application when it is integrated with all other
applications is called system testing.

EXPLORATORY TESTING
When there is a requirement or an application to test
but with no relevant document or details provided to
tester the tester explores the application and keep
checking the features to figure out the issues is
known as Exploratory Testing.
It’s a format of unstructured testing.

UAT
▶ UAT stands for User Acceptance Testing
▶ Where the product is evaluated as per the end
user’s requirement
▶ Performed by the end users or stakeholders
▶ Product is evaluated that whether it matches with
business requirement or not and whether to
accept or reject the product
▶ Usually the last type of testing
▶ UAT has 2 types Alpha testing and Beta Testing

Alpha & Beta Testing
Alpha Testing Beta Testing
Performed by testers in testing
environment
Performed by real end users in live
environment
Alpha Testing performed at
developer's site
Beta testing is performed at client
location or end user of the product
Alpha testing comes before beta
testing
Beta testing is performed after alpha
testing
Alpha testing involves both the white
box and black box techniques
Beta Testing typically uses black box
testing
Alpha testing is conducted within the
organization and tested by
representative group of end users
Beta testing is conducted by the end
users

NON-FUNCTIONAL
TESTING TYPES EXPLAINED
on next level
Video 10

PERFORMANCE TESTING
Performance testing is a test done to determine how a
system performs in terms of speed, load and stability
under a particular workload
Performed to check the reliability of the application.
Performance testing types are:
▶ Load Testing
▶ Stress Testing
▶ Soak Testing

PERFORMANCE TESTING TYPES
Load Testing
Load testing is done to determine how the application
behaves under a specific load. Example - Check that
what is the page load time if 10 concurrent users
access the same page at a time

Stress Testing
This testing is performed to check the breakpoint of
the application so that the team can plan for load
balancer.

Soak Testing
Soak testing is done to check that how the
application behaves when the app gone through
under a specific load for a specific time.

SECURITYTESTING
Security testing is a testing process intended to
reveal flaws in the security mechanisms of an
application to protect data, sensitive information.
▶ This testing is done to check the vulnerabilities in
the application and fix it.
▶ To ensure that the sensitive data travels in
encrypted format
▶ To insure that no unauthorized access can be
made

COMPATIBILITY TESTING 1/2
▶ Compatibility Testing is done to check the
application’s responsiveness across various OS,
Devices & browsers.
▶ This testing is done to check the applications
rendering and usability
▶ This testing is done to make sure that all target
devices are covered

COMPATIBILITY TESTING 2/2
Use cloud service to perform compatibility testing
Saucelabs
Browserstack
Or, use google chrome developer mode to check the
responsiveness

COMPATIBILITY TESTING
A snippet of Browserstack.com responsive test page

SOFTWARE BUG/DEFECT
In general software testing language “During an
application testing any deviation in actual result and
expected result is called a bug.”
whereas Bug and Defects has slightly difference:
BUG:
DEFECT:
FAILURE:

BUG, DEFECT & FAILURE
BUG:
A bug is the result of a coding error. Bug is the
general term used for all issues caught in testing
environment.
DEFECT:
A defect is a deviation from the requirements. Defect
word is used by the business persons or stakeholder.
FAILURE:
Any issue which is passed to live users and impacting
the applications motive is called a product failure.

How to raise a Bug?
Consider the below mentioned 10 point as a must to
raise an effective bug
1) Summary
2) Description
3) Component or Assigned to
4) Steps to reproduce with Test Data and URLs
5) Logs & screenshot
6) Requirement reference
7) Release Name /Build Number / Sprint name
8) Environment
9) Priority
10)Severity

PRIORITY & SEVERITY
Priority
The impact of the bug or function on business level
is called priority.
Priorities are defined as : P1, P2 & P3
Severity
The impact of the bug or function on Application
level is called priority.
Severities are defined as : Major, minor, critical,
blocker

BUG MANAGEMENT TOOLS AND
IMPORTANCE
▶ BugZilla
▶ Mantis
▶ Hp-QC or HP-ALM
▶ Zira

NON REPRODUCIBLE BUGS
When a tester reports a valid bug but the same bug
can not be reproduced by others due to any reason is
called a non-reproducible bug.
The reason could be :
1) Test Environment
2) Test locations
3) Test Data
4) System configuration
5) System of server cache memory

How to deal with NON REPRODUCIBLE
BUGS
▶ Provide proper story and not just steps
▶ Record a video or capture a screenshot for proof
▶ Provide the system log, application log and server
logs
▶ Provide the time of execution
▶ Provide the location of test execution
Try to reproduce the bug by clearing the system
cache memory
Try to clear the server side cache (to clear the server
side cache put ?nocache=1 at the end of the URL
and hit enter)

TEST MANAGEMENT TOOLS
Video 12

TEST MANAGEMENT TOOL
“Test Management tools are the tools required to
manage whole testing activity and reporting in an
organized manner.”

TEST MANAGEMENT TOOL
Feature
1: Manage the build and versioning for test
2: To manage the Test scenarios, Test Case and Test
scripts
3: To map the requirements and test scenarios, test
cases
4: To update the test case status while executing
5: To update the test cases with a defect
6: To track the test progress
7: To generate the test report
8: To maintain the test history

TEST MANAGEMENT TOOLs
▶ HP ALM (Application lifecycle management) or HP-
QC (Quality centre, is the older version of ALM)
▶ JIRA
▶ q-Test
▶ Testlink
▶ Zephyr

A DETAILED EXPLANATION OF SCRUM METHOD
AGILE MODEL
Video 13

• A SDLC model to build an application fast in very
short span of time
• Delivers workable modules after each release
• Development and Testing goes side by side
• A combination of iterative and incremental
approach
Agile is:

“Waterfall model is a sequential development model
where each phase of SDLC is executed one after
another in a linear way so its also called linear
sequesntial model”
Waterfall Model:
REQUIREMENT
DESIGN
DEVELOPMENT
TESTING
DEPLOYMENT
MAINTENANCE

Agile vs Waterfall model
Waterfall Agile
A sequential process; once a step
has been completed, developers
can’t go back to a previous step.
Agile came about as a “solution” to the
disadvantages of the waterfall. Quick and
easy develop and deploy
Waterfall methodology relies
heavily on initial requirements. NO
further changes allowed.
The Agile methodology allows for changes to
be made after the initial planning.
If a requirement error is found, or
a change needs to be made, the
project has to start from the
beginning
It’s easier to add features that will keep you
up to date
The whole product is only tested at
the end so bugs caused by very
initial phases will be detected at
later stage
The requirements are tested from the very
beginning so early detection of bugs is an
advantage.

• Sprint & Scrum
• Lean & Kanban
• XP (Extreme Programming)
• RAD (Rapid Application Development)
Agile Methods

• Scrum is an Agile development method
• Simple way to implement agile in product
development
• Its Management and control process for development
and testing
• The product is developed in an incremental order
Scrum

Roles
Product Owner Scrum Master Scrum Team Members
A person from business
end
Facilitator for PO and
Team
Cross-functional group of
people
Managing product
Backlogs
To clear the hurdles
faced by team
Estimates the size and
complexity of the work
Prioritizes and refines the
backlog
Makes sure team is
following the agile
practices
The core technical team that
works on requirements
person to add the tasks in
sprint and approve the
demo in product review
Set up sprint planning,
scrum meeting , review
and retrospective
Design, develop and test the
business requirements

Scrum Lifecycle in Agile
1. Product
Backlog
2. Sprint
Meeting
Sprint
1-4
weeks
4. Daily Scrum meets or
stand-ups
6. Sprint
Retrospective
5. Sprint Review (Demo
product)
3. Task
Burndown
Shippable
product
Agile – scrum lifecycle
(Source: wiki)

sprint planning
• Sprint Window : 1 week (5 days)
• Per day workable hours : 6 hrs
• Resources (2 developer & 2 tester) : 4
Total time : 5*6*4 = 120 hrs
Task1 - Estimated time = 10hrs
Task2 - Estimated time = 5 hrs

Product Backlog
“A product backlog is a prioritized list of
business requirements”
A typical Scrum backlog comprises the following different types of
items:
• Features
• Bugs
• Non-functional features
• or any other technical stuff

Sprint planning
“In scrum methodology each work
iteration is called a Sprint.”
• Every Scrum begins with the sprint planning meeting.
• In which the Product Owner and the team(s) discuss which stories will
be moved from the Product Backlog into the sprint backlog.
• It is the responsibility of the Product Owner to determine what work
the team will do.
• Once the team commits to the work, the Product Owner cannot add
more work or micromanage.
• The Product Owner can cancel a Sprint, which shouldn’t happen often,
and would usually occur due to a sudden change in business needs.

Scrum Meeting or stand-ups
“Standup meetings are the daily 15
minutes catch up among all team
members and scrum master, where they
update each other about
• what they did the previous day
• what they will do today and
• what are the road blockers.”

Burndown
“A burndown chart is a graphical
representation of work left to do versus
time”
The daily analysis of task remaining and time remaining to complete the
sprint and assess whether we are on time or behind the schedule.

“Sprint review meet is held at the end of each
sprint and a demonstration of developed work
will be done to stakeholders”
The meeting itself should be strictly time boxed to no more
than an hour per week of Sprint. So a two-week Sprint would
have a two-hour review and a one-week sprint a one-hour
review.
▶ Reviews the work that was completed and the planned work
that was not completed
▶ Presents the completed work to the stakeholders
Sprint Review

Sprint Retrospective
“At the end of the sprint whole team gathers to reflect
how things went and what they’d like to change. This
meeting is called the Sprint Retrospective meeting.”
Take away:
1: What worked well
2: What didn’t work well
3: Actions to improve

Jira
● Jira is a tool developed by
Atlassian an australian
company
● It’s a project management
and bug management tool
● Jira is a truncation of
Gojira, the Japanese name
for Godzilla

Jira
Epic: An epic captures a large body of work. It is
essentially a large user story that can be broken
down into a number of smaller stories. It may take
several sprints to complete an epic.
Story: A story or user story is a software system
requirement that is expressed in a few short
sentences, ideally using non-technical language.
Task: A task is a unit of work contained within a
story. In JIRA Agile
Sub-task: A individual task within a task in called a
sub task

INTRODUCTION TO
AUTOMATION TESTING
& CONTINUOUS INTEGRATION TESTING
Video 14

INTRODUCTION
● Automating the manual testing process by using
any tool is automation testing.
● Using a tool to execute the test cases is
automation testing.
● Test automation requires the significant amount
of Money and skills.
● Significant amount of time can be saved by
automation
● Not everything can be automated

MANUAL vs AUTOMATION
Manual Automation
Manual Testing is done manually by
humans
Automation testing is done with the help
of a tool
To test the same thing it takes much
time
It takes less time in execution but
writing automation script may take
longer time
More resource required Less resource required
New features are usually tested
manually first
regression test cases are executed with
automation
Executing same test cases on multiple
environment is very time consuming
Same automation script can be run on
multiple machines
Manual testing is not accurate at all Automated testing is more reliable, as it

When to automate
● High Priority - Business Critical features
● Test cases that are executed repeatedly
● Test Cases that are very tedious or difficult to
perform manually
● Test Cases which are time consuming

When not to automate
● Exploratory Testing
● Ad-hoc Testing
● Usability Testing

Continuous integration
Continuous Integration (CI) is a development practice
that requires developers to integrate code into a
shared repository several times a day. Each check-in
is then verified by an automated build, allowing
teams to detect problems early.
By integrating regularly, you can detect errors
quickly, and locate them more easily.

Continuous integration Testing (CIT)
Architecture - in Agile model

Benefits
● Faster than the manual execution
● Reliable and accurate test results
● Saves time and cost
● Reusable test scripts
● Increased efficiency
● Tests can be triggered automatically based on
some conditions
● Early Testing can be obtained

Tools
Testing Type Automation Tool
Functional & Regression Testing ● Selenium WebDriver
● HP UFT (QTP)
● WATIR
● Silktest
● Rational Functional Tester
Client side performance testing ● JMeter
● Load Runner
● Neo Load
Server side performance
testing
New Relic
API Testing ● JMeter
● ReadyAPI
● POST MAN

WHAT TO TEST IN A
WEBSITE & A MOBILE APP
Video 15

What to test in a Website
INTRODUCTION
Two broad testing types
● Functional Testing
● Non Functional Testing

What to test in website
Functional Test
● Smoke or sanity testing
● Functional Test
○ Check the newly added / modified
features for latest release
○ Check all internal/External links
○ Check the form/field validations
○ Check the submit actions for forms
○ Check the database connection and
integrity
● Regression Test

What to test in website
Non-Functional Test
● Performance Testing
○ Check the Page load times on different net speeds
○ Test the page response times on different loads
○ Check the server response time
○ Check that whether your application assets are optimized or
not
○ Test with: https://testmysite.thinkwithgoogle.com/ gives
very useful details about your website
● Security Testing
● Compatibility Testing
○ Test to check the application's responsiveness on different
different devices, Oss, browsers and browser versions
● Usability Testing
○ Test for Navigations
○ Test for look and feel (no overlapping, Website
instructions,Error msgs)

What to test in a Mobile app
INTRODUCTION
● Device specific Tests
● Network specific Test
● App Functional-NonFunctional Tests

What to test in Mobile app
DEVICE SPECIFIC TESTS
1 Check the App installation/uninstallation in device
2 Check the launching of the app in device(verify splash screens, load time,
presentation)
3 Connect/Disconnect the charger, check that the running app is not impacted
4 Lock/unlock the screen and check that running app has no impact
5 Go to home and come back to your app (sleep the app)
Check that you can switch to other apps in device smoothly
6 Tilt and shake to check the impact on your running app
7 Check the device notifications are not impacting the running app
8 Check that no data network connection is displayed if your app needs a data
connection
9 Check that app interacts with device hardware (like GPS)
10 All device buttons have associated action for your app

NETWORK SPECIFIC TESTS
1 Check the App behavior on 2G, 3G and WiFi internet connections
2 Check the App behavior in no network condition
3 What happens if user switch from one data network to another
4 Lock/unlock the screen and check that running app has no impact
5 Interruption Testing : Does the app resumes when a call comes
6 Interruption Testing : Does the app resumes when a message comes
7 Check the device notifications are not impacting the running app
8 If app has a transaction system then how the transaction behaves during
network fluctuations
9 Check the app’s background data connections can be changed
10 How app behaves in Flight Mode

Functional/NonFunctional
Functional - During this testing tester has to focus on the business requirements
that the application must deliver or perform
Non-Functional -
Check the application’s heap memory
Check the application’s RAM memory usage
Check the application’s CPU usage
Compatibility: On different OS versions and on different Devices
Usability: Check that user has no issue with the usability of the app
Check that the cache memory can be cleaned
Check the app’s performance on different sets of configurations

International Software Testing Qualification Board
TIPS TO CLEAR ISTQB-
FOUNDATION LEVEL
CERTIFICATION
Video 16

INTRODUCTION
● International Software Testing Qualification Board
● Is a software testing qualification certification
organisation that operates internationally
● Founded in Edinburgh in November 2002
● ISTQB is a non-profit association legally registered
in Belgium
● The ISTQB® is a software testing qualification
certification organization having over 350,000
certifications issued.
● The ISTQB® consists of 49 member boards
worldwide representing 72 countries
● Official site http://www.istqb.org/

ISTQB CERTIFICATION
There are three levels of certification:
● ISTQB Certified Tester Foundation Level (CTFL)
● ISTQB Certified Tester Advanced Level (CTAL)
Test Manager
Test Analyst
Technical Test Analyst
Advanced Level (CTAL) - Full Advanced Level (after passing the above
exams of Advanced Level)
● Expert Level
Improving the Test Process
Test Management
Test Automation
Security Testing

FOUNDATION LEVEL
CERTIFICATION
The Foundation level offers the following exams:
★ Foundation level core (1 syllabus )
★ Foundation level specialist(4 syllabi, two of them
currently available, two of them undergoing
development)
★ Agile Tester
★ Model-Based Tester
★ Usability Tester (in development)
★ Automotive Tester (in development)

PASSING SCORE
● Total 40 questions (at least 26 questions should
be right)
● Time: 1hr (15 minutes Extra for non-native
language person)
● Passing Score 65%
● Fees - 4500 INR
if reappearing - 2800 INR
...and No Negative marking :)

How to clear ISTQB tip 1
Go through the ISTQB syllabus
Find the updated syllabus here (official ISTQB site):
Link: http://www.istqb.org/downloads/syllabi/foundation-level-
syllabus.html

Go through the ISTQB book at least once
Download the e-books from here (official ISTQB site)
Link: http://www.istqb.org/downloads/e-books.html

Go through the ISTQB Exam documents
Exam Document here:
Link: http://www.istqb.org/downloads/exam-documents.html

Practice the mock questions
Search for the sample papers and keep practicing the exercises.
A good collection is here:
http://istqbexamcertification.com/istqb-dumps-download-mock-tests-
and-sample-question-papers/
This will help you out to find your weak areas, practice more on
that.
But never rely completely on sample questions as these are not
the one that will show up in exam.

Make a list of terminologies and keep checking
that.

Almost all the answer options will look similar so
always read carefully and understand properly.
so read questions carefully
and read the options too… double check!

Software testing course - Manual

More Related Content

What's hot (20)

Similar to Software testing course - Manual (20)

Recently uploaded (20)

Software testing course - Manual