Added accessibility and load tests in docs

Arquisoft · May 1, 2024 · 7641805 · 7641805
1 parent e2f394a
commit 7641805
Show file tree

Hide file tree

Showing 8 changed files with 42 additions and 4 deletions.
diff --git a/docs/images/accessibility_game_desktop.png b/docs/images/accessibility_game_desktop.png
diff --git a/docs/images/accessibility_game_mobile.png b/docs/images/accessibility_game_mobile.png
diff --git a/docs/images/accessibility_menu_desktop.png b/docs/images/accessibility_menu_desktop.png
diff --git a/docs/images/accessibility_menu_mobile.png b/docs/images/accessibility_menu_mobile.png
diff --git a/docs/images/gatling_test_01.PNG b/docs/images/gatling_test_01.PNG
diff --git a/docs/images/gatling_test_01_graphics.PNG b/docs/images/gatling_test_01_graphics.PNG
diff --git a/docs/images/gatling_test_02.PNG b/docs/images/gatling_test_02.PNG
diff --git a/docs/src/12_testing_report.adoc b/docs/src/12_testing_report.adoc
@@ -20,8 +20,20 @@ Our end-to-end approach focused on this functionality:
 - Game result
 - Login / register
 
-=== 12.3. Gatling tests
-TODO when deploys
+=== 12.3. Load tests
+Load tests are conducted to assess performance under anticipated normal or peak loads. For these tests,
+we utilized the Gatling tool, enabling the recording of a usage scenario and adjusting the load intensity accordingly.
+
+We approached our testing by simulating gameplay with multiple users, employing two distinct scenarios.
+In the first scenario, we initially load 205 requests simultaneously, followed by a 5-second pause. Subsequently,
+we introduce an additional 401 requests distributed over 21 seconds, concluding with a load of 48 users per second maintained for 16 seconds.
+
+image::gatling_test_01.PNG["First gatling test", align="center"]
+image::gatling_test_01_graphics.PNG["Graphics of the first gatling test", align="center"]
+
+In the second scenario, we initiated 26060 requests, of which 18935 passed succesfully, with a response time lower than 1200 ms, and 7125 that failes, leaving it with a percentaje of failure of  27%.
+
+image::gatling_test_02.PNG["Second gatling test", align="center"]
 
 === 12.4. Usability tests
 
@@ -65,5 +77,31 @@ low time, all geography categories, wrong password message not found
 | nothing to highlight
 |===
 
-=== Improvements based on usability testing
-Added more time to answer the questions and how to play menu
+==== Improvements based on usability testing
+Added more time to answer the questions and how to play menu
+
+=== 12.4. Accessibility tests
+Accessibility testing is a critical aspect of web development, ensuring that websites are usable by all individuals.
+By conducting accessibility tests, we can identify and address potential barriers that may prevent users from accessing or interacting with our website effectively.
+Our team is committed to creating an inclusive and accessible website that meets the needs of all users, regardless of their abilities or limitations.
+
+Using lighthouse, we tested two of the views of our website, the home page, and the game page. The results are shown below.
+
+==== Menu view
+With the desktop setting we got good results:
+
+image::accessibility_menu_desktop.png[Accessibility menu desktop, align="center"]
+
+With the mobile setting we got worse results, but as expected as the application is not fully accommodated to smaller screens.
+
+image::accessibility_menu_desktop.png[Accessibility menu mobile, align="center"]
+
+==== Game view
+With the desktop setting we got good results, a bit worse than the menu:
+
+image::accessibility_game_desktop.png[Accessibility game desktop, align="center"]
+
+Same happens with the mobile setting
+
+image::accessibility_game_mobile.png[Accessibility game mobile, align="center"]
+