This document outlines the guidelines for error messages in our code repository. We want to ensure that error messages are formatted consistently and do not include newline characters, as this can disrupt testing and matching messages.
All error messages in this code repository should follow the same format. Each error message should start with 'ERROR:', followed by the specific error description. Error descriptions should adhere to the following patterns:
-
For updates, use the following format:
ERROR:(.*?)Update
-
For deletions, use the following format:
ERROR:(.*?)Delete
-
For employee-related errors, use the following format:
ERROR:(.*?)Employee
By adhering to these formats, we maintain consistency in our error messages and make it easier for developers to understand and handle errors.
You should now be capable of testing with errors.
Please remember to utilize 'cout' instead of 'cerr.'
It has been noted that @itu-itis22-saydamm21's solution employs the '\n' character rather than 'endl'.
Here's an example of a correctly formatted error message:
'ERROR: not valid Id To Update' or 'ERROR: AN invalId Id To update'. Anything in between 'ERROR:' and 'U/update' shouldn't matter when testing with test_with_errors.yaml file.
It is your responsibility to edit your error messages to comply with the assignment PDF when submitting.
Please follow these guidelines when creating error messages in our codebase. Consistency in error messages enhances the debugging process and improves the overall quality of our code.
If you have any questions or need further clarification, please don't hesitate to reach out to the team.
Happy coding! 🚀