Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added usability tests to the documentation #173

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/images/12-usability-graph-01.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/12-usability-graph-02.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
18 changes: 17 additions & 1 deletion docs/src/12_testing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -42,4 +42,20 @@ The first ones were designed to test the application under "normal" circunstance
- **1200 users playing normally**: Arriving in batches of 100 people per second over 12 seconds. They log in, play and check the results. -> link:https://github.com/Arquisoft/wiq_en1b/files/15139645/burstlogin.pdf[Result PDF]

As we can see, in the first kind of testing, the percentage of successful requests is between 99 and 100%. However things change when moving into the second kind, with a success rate of 91% for the ones playing as a guest and 82% for the ones logging in.
Despite not being such great numbers as the other ones, this still represent a lot of successes under a very stresfull situation for our application.
Despite not being such great numbers as the other ones, this still represent a lot of successes under a very stresfull situation for our application.

=== Usability testing

==== Analytical information
After performing test with various people from various age groups we were able to extract information about the times they apent in the application. As we can see, the ones below 20 years of age perform much better than expected, while the ones between 40 to 60 years performed worse.
The surprisingly good performance of the first age group might be because of the colourful and very graphical navigability of the application, which allow them to grasp every component and their inner workings really quickly.
While this same thing might have been the bane of the older age groups, since they struggle more with the navigability and where trying to read more instead of focusing on the icons.

image::12-usability-graph-01.png["Average response times by age group"]

We can also see in which parts of the application they have spent the longest. We can see how it's pretty evenly distributted. This should come as a surprise, considering that they did play a competitive game (which are pretty short).
This is thanks to the more speedy users, which brought the average down quite significally. Since the difference between one user and another are very small in the duration of the games, but massive in the logging and set up.

image::12-usability-graph-02.png["Average time spent on each part of the application"]

A potential problem could have been the small sample size, so further tests are recommended, with a similar amount of users in each age group.