| Both sides previous revision Previous revision Next revision | Previous revision |
| report:intro [2026/05/31 14:56] – [Usability Testing] team6 | report:intro [2026/06/03 15:01] (current) – [Web Application Stress Testing] team6 |
|---|
| |
| <WRAP centeralign> | <WRAP centeralign> |
| <figure fig:webapp-stresstest-results> | <figure fig:webapp_stresstest_results> |
| {{ :report:webapp-stresstest-results.png?400 |}} | {{ :report:webapp-stresstest-results.png?400 |}} |
| <caption>k6 load test results for the web application</caption> | <caption>k6 load test results for the web application</caption> |
| </WRAP> | </WRAP> |
| |
| As shown in Figure 1, the application processed 1,130 HTTP requests with a failure rate of 0.00%. All checks were completed successfully: 1,130 out of 1,130 checks were completed. The average response time was 34.21 ms, and the response time at the 95th percentile was 95 ms, which is well below the set limit of 2,000 ms. | |
| | As shown in Figure {{ref>fig:webapp_stresstest_results}}, the application processed 1,130 HTTP requests with a failure rate of 0.00 %. All checks were completed successfully: 1,130 out of 1,130 checks were completed. The average response time was 34.21 ms, and the response time at the 95th percentile was 95 ms, which is well below the set limit of 2,000 ms. |
| |
| These results demonstrate that the web application remained stable and responsive under the tested load. Since the test was limited to 5 virtual users, it should be considered an initial performance test rather than a full-scale stress test. | These results demonstrate that the web application remained stable and responsive under the tested load. Since the test was limited to 5 virtual users, it should be considered an initial performance test rather than a full-scale stress test. |
| The usability test was designed as an online survey. Participants were asked about their first impression of the application, the clarity of the layout, the ease of use of the main features, and whether the design seemed suitable for children aged 6 to 13. | The usability test was designed as an online survey. Participants were asked about their first impression of the application, the clarity of the layout, the ease of use of the main features, and whether the design seemed suitable for children aged 6 to 13. |
| |
| {{ :report:usability-test-results.png?400 |}} Figure X: Overview of the responses to the Healing Cocoon usability test. | <WRAP centeralign> |
| | <figure fig:usability-test-results> |
| | {{ :report:usability-test-results.png?400 |}} |
| | <caption>Overview of the responses to the Healing Cocoon usability test.</caption> |
| | </figure> |
| | </WRAP> |
| |
| The survey was completed by 4 participants. The average completion time was 4 minutes and 53 seconds. Given the limited number of participants, the results should be viewed as early feedback and not as final validation. | The Figure {{ref>fig:usability-test-results}} shows that the survey was completed by 4 participants, and the average completion time was 4 minutes and 53 seconds. Given the limited number of participants, the results should be viewed as early feedback and not as final validation. |
| |
| Overall, the feedback was positive. Participants generally found the layout clear and the main functions user-friendly, such as choosing a world, starting a session, and understanding the sound and scent settings. The breathing exercise was also found to be helpful by the participants. | Overall, the feedback was positive. Participants generally found the layout clear and the main functions user-friendly, such as choosing a world, starting a session, and understanding the sound and scent settings. The breathing exercise was also found to be helpful by the participants. |