diff --git a/index.html b/index.html index 4463aa26..360b809a 100644 --- a/index.html +++ b/index.html @@ -527,9 +527,8 @@

WIQ Docum
  • 12.2. e2e Testing
  • 12.3. Code coverage
  • 12.4. Usability and accessibility Testing
    • -
  • 12.5. Testing with real users:
    • -
  • 12.6. Load Testing
    • -
  • 12.7. Code coverage
    • +
  • 12.5. Load Testing
    • +
  • 12.6. Code coverage
  • 13. Glossary
    • @@ -1745,6 +1744,11 @@

    12.3. Code coverage

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

    +
    +
    +12 sonarcloud +
    +

    12.4. Usability and accessibility Testing

    @@ -1756,9 +1760,8 @@

    12.4.1. Automatic tools:

    First, we will show the automatic tools results:

    -
    -
    -

    12.4.2. PageSpeed Insights:

    +
    +
    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:

    @@ -1778,8 +1781,8 @@

    12.4.2. PageSpeed Insights:

    warning because we don’t use HTTPS in our application, which can lead to security issues.

    -
    -

    12.4.3. Juicy Studio:

    +
    +
    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:

    @@ -1799,8 +1802,8 @@

    12.4.3. Juicy Studio:

    -
    -

    12.5. Testing with real users:

    +
    +

    12.4.2. Testing with real users:

    We did some testing with 18 people, all of them being friends and family of us, the develpoment team. We let them try the application, play games, view their stats, create groups, etc., and when they were @@ -1837,8 +1840,9 @@

    12.5. Testing with real users:

    We should also consider improving our UI, maybe studying design tendencies and trying to applicate them to our project.

    +
    -

    12.6. Load Testing

    +

    12.5. 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:

    @@ -1888,7 +1892,7 @@

    12.6. Load Testing

    -

    12.7. Code coverage

    +

    12.6. Code coverage

    We used SonarCloud to check the code coverage of the application. It shows test coverage, code duplication, and code smells, among other things. The results are shown below:

    @@ -1984,7 +1988,7 @@

    13. Glossary