1 of 18

��Game Dragons Out�by Michal Pilarski��inspired by �Dragons Out book

© Dragons Out Oy

1

2.3.2022

2 of 18

After reading Dragons Out…

  • This book reminds me of my adventure a few years ago when I was young ☺ and spent my vacation in Southern Poland on the Path of Eagles Nests, where, with my family, I visited many Castles and chased…

2

3 of 18

… Dragons and…

3

4 of 18

… of course many were defeated ☺

4

5 of 18

After reading Dragons Out…

  • This book reminds me that having fun during work is very important for balance and good atmosphere

​

  • This book reminds me that storytelling makes miracles

​

  • This book showed me Testing Software from another perspective, proving that it is not only for kids ☺ (or maybe I am still a kid)…

5

6 of 18

This resulted in my head doing something more than only reading…

6

7 of 18

I created… THE GAME

7

8 of 18

GAME Dragons Out

Not only for Kids

Overview

​

The game was created in Scratch for Kids – a block/puzzle graphical programming environment to summarize the book.

​

The most known types of dragons try to threaten the Castle by attacking a huge pack, one by one. Two players - The Sage and The Archer, are sent on a dangerous mission to defend the Castle against the creatures.

​

The Game’s main goal is to defeat all 7 dragons representing different defects.

​

Players have 3 lives, can be moved horizontally, and can send projectiles to hit dragons. Dragons move from left to right and return. Dragons send fireballs and try to hit players. If a specific dragon appears then the respective defect is triggered and makes game level harder.

​

Who wins!?

Good luck, heroes!!

8

9 of 18

How to play?

Moving player

9

Arrow or iceball shot

Click to switch players

Number of defeated dragons

Number of lives

Players/dragons

Projectiles

Stop game

Start/Stop game and enable/disable fullscreen

10 of 18

Players

  • Head Sage Cho as Wizard
  • Shepherd Laura as Archer

​

10

11 of 18

Annoying dragon

  • Defect name: Memory leak
  • Severity: Medium
  • Defect symptoms: The computer gets slower, until it can’t function at all, and it shuts down
  • Cause of the defect: Memory is reserved for use of the software, but it is not freed after usage
  • Root causes: Developer is not careful in freeing the memory. May not know how, may not remember.
  • Testing: You measure used memory as you use the software. If the amount of used memory increases all the time, it is probably a memory leak.
  • Fix: You run the software one line of code at a time, until you find the spot that should be fixed. Memory is released with a proper piece of code.
  • Game: The shooting performance is broken. Slowing down opponent projectiles. It is really hard to hit.

© Dragons Out Oy

11

2.3.2022

12 of 18

Robbing dragon

  • Defect name: Functionality defects
  • Severity: Low-Medium-High
  • Defect symptoms: The software doesn’t do what it should do. Calculation gives wrong result. User sees information in the wrong place.
  • Cause of the defect: The functionality has been coded wrong.
  • Root causes: Developer has not understood what the user has meant. Or the defect exists due to carelessness, or hurry.
  • Testing: You use the software normally, based on tester experience or requirement definitions.
  • Fix: Code is changed to work correctly.
  • Game: The functionality of shooting is broken. Temporary change in the range of opponent projectiles. The player cannot hit the dragon for a few seconds.

​

© Dragons Out Oy

12

2.3.2022

13 of 18

Mean dragon

  • Defect name: Security defect
  • Severity: High
  • Defect symptoms: Information from the software is found outside the system (e.g. bank card information). It could also be just software functioning wrong.
  • Cause of the defect: A criminal has used security defect to break into the system, and then has stolen or destroyed something.
  • Root causes: Developer has not followed the latest secure coding principles. Maybe doesn’t know these.
  • Testing: You look for known vulnerabilities in the software by using it, or via a security testing software. You can also review code. Checklist of known defects helps.
  • Fix: A known vulnerability has also a known fix. It is fixed in the code or system settings.
  • Game: Security damaged. Temporarily, the player says secret information which should not be published.

​

© Dragons Out Oy

13

2.3.2022

14 of 18

Fast dragon

  • Defect name: Performance defect
  • Severity: Medium
  • Defect symptoms: Software is slower than it should
  • Cause of the defect: Part of the code works inefficiently or plain wrong. Settings could be wrong, too. Software then tries to do something unnecessary. This takes time.
  • Root causes: Performance wasn’t considered during coding. Developer may not know all possibilities of the coding environment. May not have access to rest of the software.
  • Testing: You use software normally, one or many users at a time, often with a performance testing software. You measure speed, that is response time.
  • Fix: You change those parts of the code that work slowly. You try a fix and test the speed again.
  • Game: Performance slowed down. Introduce lags to player movement.

​

© Dragons Out Oy

14

2.3.2022

15 of 18

Showy, troublesome dragon

  • Defect name: Usability defect
  • Severity: Low
  • Defect symptoms: Software is hard to use, but it can be done.
  • Cause of the defect: Coding is done with only functionality in mind, possibly in the easiest way.
  • Root causes: User needs have not been taken into account in design or coding. Usability may not be understood.
  • Testing: You use the system normally. You gather opinions about what is easy and what is hard to use.
  • Fix: You change the code so that the system is easier to use, respecting results from usability testing.
  • Game: Using the system effectively is broken. You can continue playing, but your movement is blurry.

​

© Dragons Out Oy

15

2.3.2022

16 of 18

Confused dragon

  • Defect name: Documentation defect
  • Severity: Low
  • Defect symptoms: Functionality works in a different way than the documentation says. 
  • Cause of the defect: Plans and guidelines are not aligned with the software.
  • Root causes: There have been decisions or changes during coding that have created a different software than planned. Documentation has been created based on old plans.
  • Testing: You use the system normally. If a defect is found, you consider if the software or the documentation is wrong.
  • Fix: You change either the software or the documentation, so that they match.
  • Game: The object on the screen looks different to the documentation. The displayed player costume does not meet the requirements. The player’s costume changes into a Dragon.

​

© Dragons Out Oy

16

2.3.2022

17 of 18

Underground dragon

  • Defect name: Hardware defect
  • Severity: High
  • Defect symptoms: Some part of or all of the computer doesn’t work.
  • Cause of the defect: A part of hardware has broken over time.
  • Root causes: A part of hardware may be of low quality, so it doesn’t last as long as it should. Possibly the part doesn’t work well with other parts, so it breaks.
  • Testing: You use the system normally. You observe the hardware. Test environment uses similar hardware than the users will have.
  • Fix: You change a broken part to a new one or change to a part that better fits other parts.
  • Game: Hardware Screen is broken. Nothing is being displayed. The player costume is invisible.

​

© Dragons Out Oy

17

2.3.2022

18 of 18

I dedicated that game for Kari…�I really enjoyed Dragons Out Story…�Good Luck in defeating Dragons…��LINK to game�https://scratch.mit.edu/projects/946359272/�

18