2017-07-16 13:28:26 -06:00
|
|
|
# Robot Simulator
|
|
|
|
|
|
|
|
|
|
Write a robot simulator.
|
|
|
|
|
|
|
|
|
|
A robot factory's test facility needs a program to verify robot movements.
|
|
|
|
|
|
|
|
|
|
The robots have three possible movements:
|
|
|
|
|
|
|
|
|
|
- turn right
|
|
|
|
|
- turn left
|
|
|
|
|
- advance
|
|
|
|
|
|
|
|
|
|
Robots are placed on a hypothetical infinite grid, facing a particular
|
|
|
|
|
direction (north, east, south, or west) at a set of {x,y} coordinates,
|
|
|
|
|
e.g., {3,8}, with coordinates increasing to the north and east.
|
|
|
|
|
|
|
|
|
|
The robot then receives a number of instructions, at which point the
|
|
|
|
|
testing facility verifies the robot's new position, and in which
|
|
|
|
|
direction it is pointing.
|
|
|
|
|
|
|
|
|
|
- The letter-string "RAALAL" means:
|
|
|
|
|
- Turn right
|
|
|
|
|
- Advance twice
|
|
|
|
|
- Turn left
|
|
|
|
|
- Advance once
|
|
|
|
|
- Turn left yet again
|
|
|
|
|
- Say a robot starts at {7, 3} facing north. Then running this stream
|
|
|
|
|
of instructions should leave it at {9, 4} facing west.
|
|
|
|
|
|
2017-12-12 18:11:43 +00:00
|
|
|
## Exception messages
|
|
|
|
|
|
|
|
|
|
Sometimes it is necessary to raise an exception. When you do this, you should include a meaningful error message to
|
|
|
|
|
indicate what the source of the error is. This makes your code more readable and helps significantly with debugging. Not
|
|
|
|
|
every exercise will require you to raise an exception, but for those that do, the tests will only pass if you include
|
|
|
|
|
a message.
|
|
|
|
|
|
|
|
|
|
To raise a message with an exception, just write it as an argument to the exception type. For example, instead of
|
2018-03-06 00:45:39 +08:00
|
|
|
`raise Exception`, you should write:
|
2017-12-12 18:11:43 +00:00
|
|
|
|
|
|
|
|
```python
|
|
|
|
|
raise Exception("Meaningful message indicating the source of the error")
|
|
|
|
|
```
|
|
|
|
|
|
2018-02-26 12:03:28 -06:00
|
|
|
## Running the tests
|
|
|
|
|
|
|
|
|
|
To run the tests, run the appropriate command below ([why they are different](https://github.com/pytest-dev/pytest/issues/1629#issue-161422224)):
|
|
|
|
|
|
|
|
|
|
- Python 2.7: `py.test robot_simulator_test.py`
|
2018-05-26 02:01:55 -07:00
|
|
|
- Python 3.4+: `pytest robot_simulator_test.py`
|
2018-02-26 12:03:28 -06:00
|
|
|
|
|
|
|
|
Alternatively, you can tell Python to run the pytest module (allowing the same command to be used regardless of Python version):
|
|
|
|
|
`python -m pytest robot_simulator_test.py`
|
|
|
|
|
|
2018-03-06 00:45:39 +08:00
|
|
|
### Common `pytest` options
|
|
|
|
|
|
|
|
|
|
- `-v` : enable verbose output
|
|
|
|
|
- `-x` : stop running tests on first failure
|
|
|
|
|
- `--ff` : run failures from previous test before running other test cases
|
2018-02-26 12:03:28 -06:00
|
|
|
|
|
|
|
|
For other options, see `python -m pytest -h`
|
|
|
|
|
|
2017-10-25 22:04:48 +01:00
|
|
|
## Submitting Exercises
|
2017-07-16 13:28:26 -06:00
|
|
|
|
2018-02-04 11:56:00 -07:00
|
|
|
Note that, when trying to submit an exercise, make sure the solution is in the `$EXERCISM_WORKSPACE/python/robot-simulator` directory.
|
2017-07-16 13:28:26 -06:00
|
|
|
|
2018-02-04 11:56:00 -07:00
|
|
|
You can find your Exercism workspace by running `exercism debug` and looking for the line that starts with `Workspace`.
|
2017-07-16 13:28:26 -06:00
|
|
|
|
|
|
|
|
For more detailed information about running tests, code style and linting,
|
|
|
|
|
please see the [help page](http://exercism.io/languages/python).
|
|
|
|
|
|
|
|
|
|
## Source
|
|
|
|
|
|
|
|
|
|
Inspired by an interview question at a famous company.
|
|
|
|
|
|
|
|
|
|
## Submitting Incomplete Solutions
|
2018-03-06 00:45:39 +08:00
|
|
|
|
2017-07-16 13:28:26 -06:00
|
|
|
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|