Testing Boot Camp

Introduction to Software Testing

1
 About

1. A story about you and I

2. About us - Why do we do what we do
3. What to expect in the next months
3. What will you learn?
4. Industries’ salaries and trends

2
 Who am I you ask?

My name: Cosmin Ciocan

My technical background: non-existent

My profession:

Software Tester - 5.5 years(Manual and

Automation)

Trainer - 1.5 years

3
 Who am I you ask?

My name: Vlad Valean

My technical background: QA Training

course

My profession:

Software Tester - 2 years

Trainer: 1 years
4
 FastTrackIT

Who are we?

Why do we do what we do?
Why do I do this?

5
 Workshop 1

… and you are?…

6
 Workshop 2

Your expectations from this course

are?
“if you can't measure it if doesn't
exist”

7
 Workshop 3 - Rules of
engagement

Let’s create some rules we want to follow, so we

have some kind of order.
 Expectations

What will I learn?

How can you make the most of this

course?

Is this course hard?

9
 QA engineer’s salaries &
roles
Let’s talk money!

QA - entry level: 300 - 500

QA - Junior level: 400 - 600
QA - Middle level: 600 - 1200
QA - Senior level: 1200 - 1800
10
11
12
What do companies look for?
1. Proactivity
2. Engagement
3. Flexibility
4. Sociability
5. Optimism
6. Team player
13
Today’s agenda
1. Finding bugs
2. General overview on testing
3. Software’s life cycle
4. Testing throughout the software
life cycle
14
Finding the ‘bugs’

15
16
17
18
19
20
21
22
23
24
General Overview – Real life examples

25
General Overview – Real life examples

26
27
28
29
30
31
32
33
34
35
36
 General overview on
testing

What is testing?
Why is testing necessary?

37
 What does a tester do?


What is a tester (in general): - > One that tests:

Give examples of testers you have encountered (any

domain)

38
 General Overview – What is
testing?

Give your own definition of what testing is

Formal definition
Informal definition

39
 General Overview – What is testing in software?

Some definitions of Testing:

“…the process of executing a program in order to certify its Quality”

“…the process of executing a program with the intent of finding errors”

“…the process of exercising software to detect errors & to verify that it

satisfies specified functional & non-functional requirements”

40
 General Overview – What is testing?
Thesaurus:

Defect
1. A flaw in a
Error component or
1. A human system that can
action that Failure
cause the Actual deviation of
produces an component or
incorrect result. the component or
system to fail in system from its
2. They are not performing its
restricted to just expected delivery,
required function. service or result.
developer’s code. 2. Alter-names:
Fault, Bug, Problem.

41
 General Overview – What is testing?
How errors occur:

No one is perfect! We all make mistakes or omissions.

The more pressure we are under the more likely we are to make
mistakes. In IT Development we have time and budgetary deadlines to
meet.
Poor training.
Poor communication.
Requirements not clearly defined -> ambiguous.
Requirements change & requirements not properly documented.
ASSUMPTIONS!
42
 General Overview – Why is testing
necessary?

Providing a measure of the current quality of the software:

1. Correctness - To requirements, documentation, website
2. Reliability - Does not crash
3. Usability - Easy to use
4. Performance - Responds quickly to user input
5. Legal requirements - ISO / copyrights

43
 General Overview – What does a tester do?


Makes sure that the SUT:

Meets the requirements that guided its design and development

Responds correctly to all kinds of inputs (test scenarios)

Performs its functions within an acceptable time

Is sufficiently usable

Achieves the general result its stakeholders desire

44
Find the bug!

45
 Software’s life cycle

Any IT company has some products they develop. They

either own the product either develop it for others.

But, there might be a few steps from an idea to the

product itself…

How are the web-products made?

46
47
Testing is a process that is required through all
the software’s life cycle

Developing good, extensive test cases is

important

No one’s perfect. Mistakes are bound to happen

48
 Roles in an IT company
So… who does what now?

Initiation – Client

System concept – Product owner + Product manager

Planning – Project manager

Requirements analysis – Business analyst

Design – Web designer

49
 Roles in an IT company

Development – Programmer

Integration & Test – QA Engineer

Operations and Maintenance – Support (Developer, QA)

Disposition – PM, Data Administrator & Security Manager

50
.

51
 General Overview – Why is testing necessary?

The cost of failures:

A single failure may incur little cost, millions or
even LIVES.
The model of cost escalation:

52
 General Overview – Why is testing necessary?
The cost of bugs

1. In April of 1999, a software bug caused the failure of a $1.2 billion

military satellite launch, the costliest accident in history

2. Software faults caused the bank accounts of 823 customers of a major US

bank to be credited with $924,844,208.32 each in May of 1996 (news
reports) – the largest such error in banking history (American Bankers
Assoc.). A bank spokesman said the programming errors were corrected
and all funds were recovered.
53
 General Overview – Why is testing necessary?
The cost of bugs

1. January of 2001: newspapers reported that a major European railroad

was hit by the after effects of the Y2K bug. The company found that
many of their newer trains would not run due to their inability to
recognise the date “31/12/2000”; the trains were started by altering the
control system’s date settings.

2. October 1999: the $125 million NASA Mars Climate Orbiter spacecraft
was believed to be lost in space due to a simple data conversion error:
the software used certain data in English units that should have been in
metric units.
54
Let’s play a game, you and I

This is a challenge

The challenge is RISK

ANALYSIS

Make a list of scenarios or

conditions that either represent
problems or can cause
problems in a level 4 self
driving car

55
56
57
 My list
Sensors: Passenger condition:
• Passengers sensors Scenarios:
Environment • Sleep/Passed out
Spoofing • Unmapped road • Any car can be stopped by putting cones
Breakdown • Drunk
• Natural disaster (or other soft barriers) around it. Forcing
• Door • Construction zone driver to exit vehicle. Carjacking made
Spoofing Map easy!
• GPS blackout
Breakdown • Tunnels • Malicious map changes
• Proximity sensors • Map mistakes • Passed out passenger being chased by
• Bridges police. Car won’t stop. When police finally
Spoofing • Excessive water • Temporary unmapped stop car, passenger wakes up and is
Breakdown • High wind detours assumed to have been evading police.
• Police signals
Car condition: • Obstruction(human, Social • Anyone can create instant traffic jam by
• Door ajar using electronic or laser based jamming
traffic cone, tumbleweed) • Carjacking system from an overpass.
• Flat tire
• Low grip tyres
• Potholes • Remote car theft
• Animals(frogs, bunnies, • Police pursuit • Humans, not feeling concerned about
• Engine problems angering a robotic driver, do not let it onto
• Engine fire bees) • Weaponized?
• Insect infestations in sensors the road, or force it off the road as an
• Runaway vehicle Cruise bombing experiment.
• Burned out brakes • Bird droppings • Responsibility in
• Extremely dense fog case of trouble • Any self-driving vehicle can be instantly
Car connectivity • Extremely dense trafic disabled by hitting the LIDAR with a
• Privacy issues hammer.
• Software upgrade • Fire/Ambulance coming (driving history monitored
• Hacked software thorough • Splattered tar on the front end from fresh
by government)
• Malicious remote • Mud asphalt may disable entire vehicle
• Car is no longer property
tracking • Leaves
• Extremely high temperatures — Company can remotely • Police at intersection making signals can’t
• Privacy violation
by companies • Blowing sand deactivate vehicle be seen by car
 Conclusions

There are many analysis methods (context driven,

visualisation, etc )

If you can break it down into smaller pieces, it’s easier

to think of things that can go wrong

Talking with someone increases the number of ideas

 Tools and extensions
Browsers: Opera, Mozilla Firefox,
Chrome, Internet Explorer

Download Jing

Jing Tutorial - How to take a screenshot

http://www.istqb.org/downloads/send/2-
foundation-level-documents/3-
foundation-level-syllabus-2011.html4
60