Updates

index.html

@@ -521,7 +521,23 @@ <h1><span class="image"><img src="./images/arc42-logo.png" alt="arc42"></span> W
 </ul>
 </li>
 <li><a href="#section-technical-risks">11. Risks and Technical Debts</a></li>
-<li><a href="#section-glossary">12. Glossary</a></li>
+<li><a href="#_testing">12. Testing</a></li>
+<li><a href="#_unit_testing">13. Unit Testing</a>
+<ul class="sectlevel2">
+<li><a href="#_auth_service_2">13.1. Auth service</a></li>
+<li><a href="#_user_service_2">13.2. User service</a></li>
+<li><a href="#_gateway_service_2">13.3. Gateway service</a></li>
+<li><a href="#_stats_service_2">13.4. Stats service</a></li>
+<li><a href="#_webapp_3">13.5. Webapp</a></li>
+</ul>
+</li>
+<li><a href="#_e2e_testing">14. e2e Testing</a></li>
+<li><a href="#_code_coverage">15. Code coverage</a>
+<ul class="sectlevel2">
+<li><a href="#_load_testing">15.1. Load Testing</a></li>
+</ul>
+</li>
+<li><a href="#section-glossary">16. Glossary</a></li>
 </ul>
 </div>
 </div>
@@ -1690,7 +1706,97 @@ <h2 id="section-technical-risks">11. Risks and Technical Debts</h2>
 </div>
 </div>
 <div class="sect1">
-<h2 id="section-glossary">12. Glossary</h2>
+<h2 id="_testing">12. Testing</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>This section details the results of the various types of tests that have been carried out with the application.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_unit_testing">13. Unit Testing</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>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:</p>
+</div>
+<div class="sect2">
+<h3 id="_auth_service_2">13.1. Auth service</h3>
+<div class="imageblock">
+<div class="content">
+<img src="./images/12-authservice.png" alt="12 authservice">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_user_service_2">13.2. User service</h3>
+<div class="imageblock">
+<div class="content">
+<img src="./images/12-userservice.png" alt="12 userservice">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_gateway_service_2">13.3. Gateway service</h3>
+<div class="imageblock">
+<div class="content">
+<img src="./images/12-gatewayservice.png" alt="12 gatewayservice">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_stats_service_2">13.4. Stats service</h3>
+<div class="imageblock">
+<div class="content">
+<img src="./images/12-statsservice.png" alt="12 statsservice">
+</div>
+</div>
+</div>
+<div class="sect2">
+<h3 id="_webapp_3">13.5. Webapp</h3>
+<div class="imageblock">
+<div class="content">
+<img src="./images/12-webapp.png" alt="12 webapp">
+</div>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_e2e_testing">14. e2e Testing</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>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.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_code_coverage">15. Code coverage</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>We used sonarCloud to check the code coverage of the application. The results are shown below:</p>
+</div>
+<div class="sect2">
+<h3 id="_load_testing">15.1. Load Testing</h3>
+<div class="paragraph">
+<p>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:</p>
+</div>
+<div class="imageblock">
+<div class="content">
+<img src="./images/12-loadtest.png" alt="12 loadtest">
+</div>
+</div>
+<div class="paragraph">
+<p>As we can see in Gatling&#8217;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.</p>
+</div>
+<div class="paragraph">
+<p>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.</p>
+</div>
+<div style="page-break-after: always;"></div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="section-glossary">16. Glossary</h2>
 <div class="sectionbody">
 <table class="tableblock frame-all grid-all stretch">
 <colgroup>
@@ -1772,7 +1878,7 @@ <h2 id="section-glossary">12. Glossary</h2>
 <div id="footer">
 <div id="footer-text">
 Version 8.2 EN<br>
-Last updated 2024-03-11 20:43:01 +0100
+Last updated 2024-04-25 18:13:16 +0200
 </div>
 </div>
 </body>