QA Workshop for our Community Management. Why do have bugs, how to report them and which kind of testing are we actually doing? Only some of the covered topics.

2. 01:0001:0000:5900:5800:5700:5600:5500:5400:5300:5200:5100:5000:4900:4800:4700:4600:4500:4400:4300:4200:4100:4000:3900:3800:3700:3600:3500:3400:3300:3200:3100:3000:2900:2800:2700:2600:2500:2400:2300:2200:2100:2000:1900:1800:1700:1600:1500:1400:1300:1200:1100:1000:0900:0800:0700:0600:0500:0400:0300:0200:0100:00
ACTIVITY
– PART
1
Requirement
gathering
Drawing
01:0001:0000:5900:5800:5700:5600:5500:5400:5300:5200:5100:5000:4900:4800:4700:4600:4500:4400:4300:4200:4100:4000:3900:3800:3700:3600:3500:3400:3300:3200:3100:3000:2900:2800:2700:2600:2500:2400:2300:2200:2100:2000:1900:1800:1700:1600:1500:1400:1300:1200:1100:1000:0900:0800:0700:0600:0500:0400:0300:0200:0100:00

3. 01:3001:3001:2901:2801:2701:2601:2501:2401:2301:2201:2101:2001:1901:1801:1701:1601:1501:1401:1301:1201:1101:1001:0901:0801:0701:0601:0501:0401:0301:0201:0101:0000:5900:5800:5700:5600:5500:5400:5300:5200:5100:5000:4900:4800:4700:4600:4500:4400:4300:4200:4100:4000:3900:3800:3700:3600:3500:3400:3300:3200:3100:3000:2900:2800:2700:2600:2500:2400:2300:2200:2100:2000:1900:1800:1700:1600:1500:1400:1300:1200:1100:1000:0900:0800:0700:0600:0500:0400:0300:0200:0100:00
ACTIVITY
– PART
2
Requirement
gathering
and
drawing

4. 4
DEBRIEFING
What
was
different
in
the
outputs?
How
did
you
feel
different?
Did
you
view
your
teammate
differently?

5. 5
2
1
3
4
5
Why Does Software
Have Bugs?
Reproducing/Reporting
a
Defect
QA
@InnoGames
BETTI
Black
Stories

6. 1

7. 7
MISCOMMUNICATION
OR
NO
COMMUNICATION

8. 8
SOFTWARE
COMPLEXITY

9. 9
PROGRAMMING
ERRORS

10. 10
CHANGING
REQUIREMENTS

11. 11
TIME
PRESSURE

12. 12
OVERCONFIDENT
PEOPLE

13. 13
POORLY
DOCUMENTED
CODE

14. 14
SOFTWARE
DEVELOPMENT
TOOLS

15. 15
OBSOLETE
AUTOMATION
SCRIPTS

16. 16
LACK
OF
SKILLED
TESTERS

17. 2

18. 18
What
is
“Reproducing
a
Defect”?
DEFINITION

19. 19
Ã Be
precise
Ã Include
exact
data
used
during
testing
for
easy
reference
Ã The
steps
have
to
be
in
the
exact
order
Ã Mention
pre-­‐requisites
when
applicable
Ã Do
not
write
composite
steps.
For
example:
If
the
scenario
requires
user
to
save
a
document
from
Microsoft
word,
then
it
should
be
written
as,
‘Open
the
File
menu
and
click
on
save
option’.
Ã Always
recheck
your
steps
to
reproduce
on
a
new
system,
clearing
all
cookies
and
cache
memory.
Ã Make
sure
the
sentences
are
short
and
unambiguous
WRITING
STEPS
TO
REPRODUCE

20. 20
Ã Look
for
similar
bug
or
patterns
Ã Watch
and
observe
every
step
Ã Use
your
creativity
to
explore
the
application
Ã Discuss
with
team
members
or
other
Community
Managers
Ã Test
with
patience
HOW
TO
REPRODUCE
A
DEFECT

21. 21
Bug
reports
help
us
in
a
myriad
of
ways:
Ã They
tell
us
about
issues
we
are
not
aware
of
Ã They
help
to
identify
new
features
that
we
may
not
have
thought
of
Ã They
help
us
get
a
feel
as
to
how
our
users
use
our
product
WHY
SEND
A
BUG
REPORT

22. 22
Ã Information:
the
more
is
supplied,
the
better
Ã Summary:
short
but
clear
– Bad:
Application
crashed
– Good:
Error
402:
Access
denied
when
clicking
‘Send
Email’
Ã Description:
where,
what
and
how
– Where
was
the
bug
found:
version,
platform,
os,
accounts
– What
is
the
issue:
detailed
description
of
the
actual
issue
and
expected
behavior
Ã Includes
all
details
about
the
issue
Ã Example
“Battles”:
type,
units,
boosts,
etc.
– How
can
the
issue
be
replicated:
the
exact
steps
how
to
reproduce
it
Ã List
of
every
single
step
which
led
to
the
issue
Ã Includes
also
all
actions
which
might
have
been
done
in
between
or
beforehand
WHAT
SHOULD
IT
INCLUDE

23. 23
Ã Be
specific
Ã Don’t
ignore
errors
Ã What
was
happening
before
Ã Attach
or
Copy
and
Paste
Ã More
is
better
It’s
not
you!
HINTS
AND
TIPS

24. 24
Q
&
A

25. 3

26. 26
We're
here
to
make
great
games
for
our
players
–
with
high
quality,
virtual
worlds
that
link
millions
of
people
around
the
world.
Anywhere,
anytime.
COMPANY MISSION

27. 27
Quality
Control
Focused
on
fulfilling
quality
requirements
QC
VS.
QA
Quality
Assurance
Focused
on
providing
confidence
that
quality
requirements
will
be
fulfilled

28. 28
Ã Testing
throughout
OVER
testing
at
the
end
Ã Preventing
bugs
OVER
finding
bugs
Ã Testing
understanding
OVER
checking
functionality
Ã Building
the
best
system
OVER
breaking
the
system
Ã Team
responsibility
OVER
tester
responsibility
TESTING
MANIFESTO

29. 29
BLACK
&
WHITE
BOX
TESTING

30. 30
UNIT
&
INTEGRATION
TESTING

31. 31
FUNCTIONAL
&
REGRESSION
TESTING

32. 32
SECURITY
TESTING

33. 33
SYSTEM
&
ACCEPTANCE
TESTING

34. 34
LOAD
&
STRESS
TESTING

35. 35
USABILITY
&
COMPATIBILITY
TESTING

36. 36
TEST
AUTOMATION

37. 37
Q
&
A

38. 4

39. 39
Beta
Testing
Tool
InnoGames

40. 40

41. 41

42. 42

43. 43

44. 44

45. 45
ADVANTAGES

46. 46
BENEFITS
New
Tools
Skills
Feature
Knowledge
Early
Feedback
Development
Process
Other
Games
Knowledge
Sharing

47. 47
PLANS

48. 48
Q
&
A

49. 5

50. 50
Players:
Ã Guess
how
the
story
came
out
Ã Ask
yes
or
no
questions
Story
Master:
Ã Can
never
lie
Ã Must
point
out
if
question
is
irrelevant
Finishing
the
Game:
Ã Ask
enough
questions
and
you
will
get
the
solution
Ã There
are
no
points,
and
loosing
means
you
probably
weren’t
thinking
out
of
the
box
enough
GAME
RULES