Skip to content

Peer Review - Consistency in Test Result Reports and Potential Use of Test-Driven Development #467

@MolyMikhail

Description

@MolyMikhail

Artifact Under Review
VnV Report

Team Number for Team Doing the Review
Team 22

Description of Issue
Great job with the report! Very detailed. One small piece of feedback is to ensure that the format of how tests are reported remains consistent throughout the report. For example, some tests are reported as "Result: Passed", while others have "Expected vs. Actual Match"; this would improve readability, especially for readers who might be unsure if there's a difference. Another suggestion relates to features that are still in progress or not yet implemented. Furthermore, test-driven development might be helpful here, where unit tests are written now with the expectation that they will initially fail but will pass once the features are implemented. This could help define the remaining requirements and ensure they are tested once implementation is completed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions