Skip to content

Commit

Permalink
Añadidas pruebas de usabilidad a la documentación
Browse files Browse the repository at this point in the history
  • Loading branch information
iyanfdezz committed Apr 27, 2024
1 parent f2618c8 commit 6f320f6
Show file tree
Hide file tree
Showing 5 changed files with 30 additions and 2 deletions.
Binary file added docs/images/juicy-dark.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/juicy-light.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/pagespeed-classic.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/pagespeed-stats.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
32 changes: 30 additions & 2 deletions docs/src/12_testing.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,42 @@ ifndef::imagesdir[:imagesdir: ../images]

This section details the results of the various types of tests that have been carried out with the application.

== Unit Testing
=== Unit Testing

We used Jest to perform unit testing on the application. We have written tests for all the components of the application, mocking the database and external services. The results of the tests are shown below:

== Code coverage
=== Code coverage

We used sonarCloud to check the code coverage of the application. The results are shown below:

=== Usability and accessibility Testing

We used some tools to measure usability levels of the application, along with some testing with real users (friends and family).

First, we will show the automatic tools results:

==== PageSpeed Insights:

This tool is used to measure different aspects of a certain page, such as performance, accessibility, best practices and optimisation.
We used this tool on all of our pages, and the results were kind of similar. Below, the results for the Classic and Stats page are shown:

image::pagespeed-stats.png[]

image::pagespeed-classic.png[]

As we can see, our pages perform very nicely on every evaluable aspect, except in Best practices, and that's because the tool is giving us a
warning because we don't use HTTPS in our application, which can lead to security issues.

==== Juicy Studio:
This tool is used to measure the contrast between background and foreground colors of a web page.
We used this tool on both of out color combinations: dark mode and light mode. The results are shown below:

image::juicy-light.png[]

image::juicy-dark.png[]

As we can see, both of our themes use correct and high-contrasted color combinations.

=== Load Testing
We used Gatling to perform load testing on the application. It consisted of simulating 1000 users accessing the application at the same time, each of one performing 83 requests. The results of the test are shown below:

Expand Down

0 comments on commit 6f320f6

Please sign in to comment.