diff --git a/images/12-authservice.png b/images/12-authservice.png new file mode 100644 index 00000000..32424cf8 Binary files /dev/null and b/images/12-authservice.png differ diff --git a/images/12-gatewayservice.png b/images/12-gatewayservice.png new file mode 100644 index 00000000..8b775971 Binary files /dev/null and b/images/12-gatewayservice.png differ diff --git a/images/12-loadtest.png b/images/12-loadtest.png new file mode 100644 index 00000000..9a1d4c4f Binary files /dev/null and b/images/12-loadtest.png differ diff --git a/images/12-statsservice.png b/images/12-statsservice.png new file mode 100644 index 00000000..9bb69e79 Binary files /dev/null and b/images/12-statsservice.png differ diff --git a/images/12-userservice.png b/images/12-userservice.png new file mode 100644 index 00000000..05312b84 Binary files /dev/null and b/images/12-userservice.png differ diff --git a/images/12-webapp.png b/images/12-webapp.png new file mode 100644 index 00000000..137e21aa Binary files /dev/null and b/images/12-webapp.png differ diff --git a/index.html b/index.html index 2d3f271f..a6c7d811 100644 --- a/index.html +++ b/index.html @@ -521,7 +521,23 @@

arc42 W
  • 11. Risks and Technical Debts
    • -
  • 12. Glossary
    • +
  • 12. Testing
    • +
  • 13. Unit Testing + +
    • +
  • 14. e2e Testing
    • +
  • 15. Code coverage + +
    • +
  • 16. Glossary
    • @@ -1690,7 +1706,97 @@

    11. Risks and Technical Debts

    -

    12. Glossary

    +

    12. Testing

    +
    +
    +

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

    +
    +
    +
    +
    +

    13. 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. All the tests passed successfully. The results of the tests are shown below:

    +
    +
    +

    13.1. Auth service

    +
    +
    +12 authservice +
    +
    +
    +
    +

    13.2. User service

    +
    +
    +12 userservice +
    +
    +
    +
    +

    13.3. Gateway service

    +
    +
    +12 gatewayservice +
    +
    +
    +
    +

    13.4. Stats service

    +
    +
    +12 statsservice +
    +
    +
    +
    +

    13.5. Webapp

    +
    +
    +12 webapp +
    +
    +
    +
    +
    +
    +

    14. e2e Testing

    +
    +
    +

    We used puppeteer to perform end-to-end testing on the application. We have written tests for login, register, create group, and for the three gamemodes.

    +
    +
    +
    +
    +

    15. Code coverage

    +
    +
    +

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

    +
    +
    +

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

    +
    +
    +
    +12 loadtest +
    +
    +
    +

    As we can see in Gatling’s report, the application was able to handle a load of 70868 requests. In particular, 81% of the requests were successful in less than 800 milliseconds, 6% in more than 1200 milliseconds and 13% were unsuccessful.

    +
    +
    +

    This shows that the application is able to handle a large number of requests in a short period of time, with a high success rate. We can also be sure that the application is able to handle a large number of users accessing it at the same time in production.

    +
    +
    +
    +
    +
    +
    +

    16. Glossary

    @@ -1772,7 +1878,7 @@

    12. Glossary