Skip to content

Test Report
Document Test Report
Author: Juuso Leppänen
Version: 0.1
Date: 22.04.2024

1. Introduction

Purpose: This test report outlines the testing conducted on the new features and enhancements introduced to Tukko, a traffic application, to ensure their functionality, reliability, and user satisfaction.

2. Test Items

The test software consisted mostly of different web browsers and extensions. The backend tests were conducted by testing the functionality of the spesified feature.

3. Test Levels

Unit Testing:
    Purpose: To test individual components or units of code in isolation.
    What was tested: Individual functions, methods, and modules responsible for specific tasks within each feature, such as user,
    color schemes, and monitoring systems.

Integration Testing:
    Purpose: To verify the interaction between different components or units of code.
    What was tested: The integration of features to ensure they work together seamlessly. For example, ensuring that
    the new color schemes and contrast adjustments interact correctly with the existing UI components.

4. Test Cases

Test Case ID: TC001
    Test Case Description: Verify Tukko runs correctly in cloud-based infrastructure using Docker.
    Test Level: Integration Testing
    Test Environment: Cloud-based server with Docker installed
    Test Execution Date and Time: 20.03.2024
    Expected Results: Tukko web page opens and datapoints are displayed.
    Actual Results: Tukko web page opens and datapoints are displayed.
    Pass/Fail: Pass

Test Case ID: TC002
    Test Case Description: Verify WIMMA Lab / IoTitude branding is changed to development team's and JAMK's branding.
    Test Level: Integration Testing
    Test Environment: Web browser
    Test Execution Date and Time: 05.04.2024
    Expected Results: Branding and logos are changed, links have been updated
    Actual Results: Branding and logos are changed, links have been updated
    Pass/Fail: Pass

Test Case ID: TC003
    Test Case Description: How dark is too dark using different browsers with existing filters and settings
    Test Level: Unit Testing
    Test Environment: Web browser
    Test Execution Date and Time: 05.04.2024
    Expected Results: Dark mode is working correctly
    Actual Results: Dark mode is working correctly, after small adjustments to the brightness
    Pass/Fail: Pass

Test Case ID: TC004
    Test Case Description: Testing of a security feature designed to enhance protection against unauthorized access,
    data breaches in a web application.
    Test Level: Integration Testing
    Test Environment: Cloud-based server with Docker installed
    Test Execution Date and Time: 07.04.2024
    Expected Results: Tukko runs and HTTPS is configured and working
    Actual Results: Tukko runs but HTTPS does not work
    Pass/Fail: Fail

Test Case ID: TC005
    Test Case Description: We are testing tukko with new color scheme so color blind people have easier time reading Tukko
    Test Level: Unit Testing
    Test Environment: Web browser
    Test Execution Date and Time: 19.04.2024
    Expected Results: Color contrast looks good and has a good ratio
    Actual Results: Color contrast looks good and has a good ratio
    Pass/Fail: Pass

5. Test Summary

Total Test Cases: 5

Passed: 4
Failed: 1
Skipped: 0

Test Case Pass Rate: 80%

Overall, the testing activities resulted in the successful execution of 4 test cases, with one test case failing to meet the expected results.

6. Defects

For each defect found, provide the following information:

Defect ID Defect Short Description
#13 Example of the Bug/Defect issue
#13 Example of the Bug/Defect issue
#13 Example of the Bug/Defect issue
#13 Example of the Bug/Defect issue
#13 Example of the Bug/Defect issue
#13 Example of the Bug/Defect issue

7. Conclusion

Based on the test results, the overall quality of the system is relatively good, with a pass rate of 80%.

The majority of the test cases passed successfully, demonstrating that Tukko runs correctly in a cloud-based infrastructure using Docker, branding and logos are updated as expected, dark mode works correctly across different browsers, and the new color scheme improves readability for color-blind users.

However, one test case (TC004) failed, indicating an issue with the security feature designed to enable HTTPS. This failure highlights a potential vulnerability in the system that needs to be addressed promptly to ensure the security and integrity of user data.

Overall, while the system shows promise with its successful test cases, the failure in TC004 indicates that further attention is needed to ensure the system's robustness and security.

8. Recommendations

Provide any recommendations for future testing activities or improvements to the system. Address HTTPS Configuration Issue (TC004): Investigate and resolve the failure in TC004 related to HTTPS configuration. Ensure that HTTPS is correctly configured and working to enhance the security of user data and communication. Implement user registration with secure database storage and two-factor authentication (2FA) to ensure user data safety and secure authentication.

9. Approvals

Specify who must approve the report.