-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simulator Test Cases #163
Comments
Editing the Task List
Since edits to an issue's description do not result in a notification, please write a comment for every edit you make to the task list, detailing the change(s) you made. Test Case TemplateA test case should be defined in the following format:
Marking Test Cases as Passed/Failed/InvalidI feel we should take from the code review concept for this, i.e. the same person should not be determining the acceptance criteria, testing the simulator on those criteria and then deciding if the simulator has passed or failed, or if the test case was in some way invalid in the first place.
I am open to suggestions on this point. |
Previously, changing the parameters of the room required carefully modifying a number of variables. This was awkward, so it was requested that it be made possible to load different pre-defined rooms based on one variable. Initially, the code was contained in the setup function in the main sketch, but it became immediately apparent that it would look messy and make the main code less maintainable if left there, so a new class was created to hold the new code. Switching between rooms is now accomplished by passing one variable to a function in the new class. To create a Room object without explicitly initializing it, a default constructor was required, so one was written. The currentPosition variable is no longer needed, since a Room object has the robot's current position as a member variable. References #163, #164.
This is intended as a master issue, allowing us to organise and track the various test cases that we may devise for the simulator. As such, each test case should be its own (sub-)issue, tracked as an item in the task list below.
The text was updated successfully, but these errors were encountered: