report:intro

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
report:intro [2026/05/28 12:14] – [Web Application Stress Testing] team6report:intro [2026/06/03 15:01] (current) – [Web Application Stress Testing] team6
Line 141: Line 141:
  
 <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>
Line 147: Line 147:
 </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.
  
 === Usability Testing === === Usability Testing ===
 +In addition to the technical tests, a small usability test was also done to get early feedback on the Healing Cocoon web application. While the stress tests focused on technical stability and performance, the usability test focused on how clear, understandable, and user-friendly the prototype felt to potential users.
 +
 +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.
 +
 +<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 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.
 +The open-ended feedback revealed that users appreciated the soothing colors, the simple layout, and the various themes, such as “Forest” and “Space.” Several potential improvements were also mentioned, such as making the “Start” button more visible and adding more options for programs, scents, visualizations, or music.
  
 +Based on this small-scale user test, the prototype appears to be intuitive and user-friendly, but further research with more participants is needed to make more definitive conclusions.
 ==== Report Structure ==== ==== Report Structure ====
 <WRAP round box 800px> <WRAP round box 800px>
  • report/intro.1779966873.txt.gz
  • Last modified: 2026/05/28 12:14
  • by team6