Arthur Freebrey - Project
  • 2D RPG
  • 1 Analysis
    • 1.1 Problem Identification
    • 1.2 Stakeholders
    • 1.3 Research
    • 1.4a Features of Proposed Solution
    • 1.4b Computational Methods
    • 1.5 Success Criteria
    • 1.6 Hardware and Software Requirements
  • 2 Design and Development
    • 2.1 Design Frame
    • 2.2.1 Cycle 1
    • 2.2.2 Cycle 2
    • 2.2.2 Cycle 3
    • 2.2.2 Cycle 4
    • 2.2.2 Cycle 5
    • 2.2.2 Cycle 6
    • 2.2.2. Cycle 7
    • 2.2.2 Cycle 8
    • 2.2.2 Cycle 9
    • 2.2.2 Cycle 10
  • 3 Testing
    • 3.1 Testing for Function and Robustness
    • 3.2 Usability Testing
  • 4 Evaluation
    • 4.1 Evaluation of Success Criteria
    • 4.2 Evaluation of Usability Features
    • 4.3 Maintenance and Future Development
    • Reference List
  • CODE
    • src
      • anims
        • CharacterAnims.ts
        • EnemyAnims.ts
      • characters
        • Faune.ts
      • enemies
        • Lizard.ts
      • events
        • EventCenter.ts
      • scenes
        • game.ts
        • GameUI.ts
        • house.ts
        • mainMenu.ts
        • PreLoader.ts
        • secondMap.ts
      • main.ts
    • index.html
    • package.json
Powered by GitBook
On this page
  • Criteria To Assess
  • Criterion 17
  • Criterion 18
  1. 3 Testing

3.1 Testing for Function and Robustness

Previous2.2.2 Cycle 10Next3.2 Usability Testing

Last updated 2 years ago

Criteria To Assess

For my success criteria I compared these tests for robustness against existing criteria I had in my 1.5 Success Criteria and see how them compare after my development.

Criterion
Description

17

The game must not crash whilst playing through

18

Game must run on at least 30fps

Criterion 17

In order to try and measure criteria 17 I must intentional perform out of the ordinary behaviour in order to try get the the game to crash such as:

  • Swapping between maps quickly

  • Hitting existing lizard coordinates multiple times

  • Speaking to the NPC characters multiple times quickly

After testing these points the game did not crash after performing these actions however I did encounter some visual glitches on the test regarding consistently speaking to the NPC multiple times. This leads me to believe the game is relatively stable and only displays visual bugs upon abnormal behaviour I have not yet fixed but nothing that would break the game and ruin the criterion.

Criterion 18

In order to measure the criterion number 18 I must display a frame counter to measure whether the game is meeting the requirement of a minimum of 30. To make sure I was testing this accurately I tried to put as much strain as possible on the game by performing abnormal behaviour such as rapid collision or changing of scenes.

Here you can see in the screenshot provided the game even after intensive usage the game always consistently on all devices I tested ran at a range of 55-60 and never dropped below the 55 mark. This shows how my game can match the criterion specified of a minimum of 30fps to make sure the gameplay stays engaging.