|
| 1 | +--- |
| 2 | +id:how-coderoad-works |
| 3 | +title:How CodeRoad Works |
| 4 | +sidebar_label:How CodeRoad Works |
| 5 | +--- |
| 6 | + |
| 7 | +###Running Tests |
| 8 | + |
| 9 | +In CodeRoad, the user is given a set of directions for a**task**. |
| 10 | + |
| 11 | +Each task is judged to pass (✔) or fail (✘) by the result of code tests that runs in the background. Tests can be triggered by saving a file, or by a trigger that listens to specific files for changes. |
| 12 | + |
| 13 | + |
| 14 | + |
| 15 | +If a test fails, the first failing test name is returned to the user as a hint to identify the problem. |
| 16 | + |
| 17 | +Tests might be in another directory. Those folders or files might even be hidden from you by the tutorial creator. |
| 18 | + |
| 19 | +But where does the code for these tests come from? |