Curricula

Objectives

The purpose of this course:
Have you ever played a shooter that crashes on intense play session? Have you found glitches that are just annoying (and sometimes quite funny!), or have you ever played a game that was clearly unfinished? It quite likely that the testers have not done their job well enough, or that the studio has had some pressure to publish a game with too little testing.
It is important for every game developer to have the basic understanding of game testing, and game testing can often serve as a way to enter into the business of game development!

Course competences:
Game production competence
Software engineering competence

The learning objectives of the course:
After completing this course you will be able to design and implement game production specific testing and quality assurance overall. You can divide the game into different levels and you can design the testing to meet these levels. You can utilize different types of testing techniques to design test cases. You can utilize your possible customers for testing purposes and use proper tools to collect data about the level of quality.

Content

In this course you will learn about the basic principles of game testing and how to manage it. In addition, we learn different game testing techniques and how to apply them in game productions. We go through the quality aspects in games and how they affect the production.

Learning materials and recommended literature

Material written by the teacher can be found at Moodle.

Teaching methods

- Lectures
- Contact lessons
- Exercises
- Final assignment
- Exam

Exam dates and retake possibilities

The exam is held at the end of the course. Renewal opportunities will be announced at the end of the course.

Alternative completion methods

You have the right to apply for recognition of your studies if you have prior learning (e.g. university studies completed elsewhere) that can be accredited towards the degree you are currently completing.

The recognition of prior learning is possible in three primary ways: accreditation (replacement or inclusion), recognition of informal learning and studification. More precise info: JAMK Degree Regulations, section 17.

Student workload

Approximately 135 hours.

Evaluation scale

0-5

Evaluation criteria, satisfactory (1-2)

Sufficient (1): You have knowledge in the area of game testing. You know the concepts and terms in game testing are what they mean. You know what kind of tools there are that can be used to support game testing in productions.

Satisfactory (2): You understand how the tools and techniques can be used to do game testing. You can design test cases and run tests in different levels of the production.

Evaluation criteria, good (3-4)

Good (3): You understand the concepts and tools in game testing and can apply them in real-life development project. You have an understanding to select the ones that suits best for the problem at hand.

Very good (4): You understand the concepts and tools in game testing thoroughly. You can analytically select correct tools and techniques and understand the testing in different types of games.

Evaluation criteria, excellent (5)

Excellent (5): You can analytically discuss about the concepts in game testing and present and defend (based on knowledge and evidence) your opinions. You can question the presented information and give valid options. You can work in a steering role in the productions.