GSoC Unit Testing

(Created page with "== Unit Testing == Often only our testers find out problems days or weeks after changes are introduced. A very simple example: any bugs that affect only a fresh start (i.e. no e...")
(Unit Testing)
Line 4: Line 4:
This project is about creating unit tests for SuperTuxKart and/or the addons/online server. Obviously there are some complications with a game like SuperTuxKart:
This project is about creating unit tests for SuperTuxKart and/or the addons/online server. Obviously there are some complications with a game like SuperTuxKart:
-
* Many errors might depend on screen resolution.
+
* Many errors might depend on screen resolution (for example icons might be missing if the resolution is too small)
-
* It is probably necessary to compare screenshots for certain type of errors, on the other hand screenshots might not be bitwise identical.
+
* It is probably necessary to compare screenshots for certain type of errors (e.g. if certain objects are not rendered on screen), on the other hand screenshots might not be bitwise identical.
* STK uses its own GUI implementation, so a way is needed to simulate things like mouse clicks etc.
* STK uses its own GUI implementation, so a way is needed to simulate things like mouse clicks etc.
== Hints ==
== Hints ==
Obviously you can use existing testing frameworks.
Obviously you can use existing testing frameworks.

Revision as of 12:59, 24 January 2014

Unit Testing

Often only our testers find out problems days or weeks after changes are introduced. A very simple example: any bugs that affect only a fresh start (i.e. no existing config files) of SuperTuxKart might go unnoticed for a long time.

This project is about creating unit tests for SuperTuxKart and/or the addons/online server. Obviously there are some complications with a game like SuperTuxKart:

Hints

Obviously you can use existing testing frameworks.

Retrieved from "http://supertuxkart.sourceforge.net/GSoC_Unit_Testing"

User Tools