Confirmed users
213
edits
Balrog: Difference between revisions
Jump to navigation
Jump to search
→Hacking: Update instructions caused by repos being merged
m (Fix repo) |
(→Hacking: Update instructions caused by repos being merged) |
||
| Line 281: | Line 281: | ||
git clone https://github.com/mozilla/balrog | git clone https://github.com/mozilla/balrog | ||
cd balrog | cd balrog | ||
== Docker == | == Docker == | ||
| Line 294: | Line 292: | ||
== UI hacking == | == UI hacking == | ||
The first build of the UI is done within docker-compose up. Nonetheless, to make code changes visible to docker you need to run: | |||
cd ui | cd ui | ||
lineman build | lineman build | ||
| Line 312: | Line 304: | ||
=== Backend === | === Backend === | ||
The recommended way to run backend tests is through Docker. Doing so will ensure your tests will run the same way they do in CI. To run them, use this command in the root of your Balrog repository: | The recommended way to run backend tests is through Docker. Doing so will ensure your tests will run the same way they do in CI. To run them, use this command in the root of your Balrog repository: | ||
./run-tests.sh | ./run-tests.sh backend | ||
If you can't or don't want to run tests within Docker for some reason, you can run them with directly with: | If you can't or don't want to run tests within Docker for some reason, you can run them with directly with: | ||
| Line 321: | Line 313: | ||
=== Frontend === | === Frontend === | ||
To run the unit tests use: | To run the unit tests use: | ||
./run-tests.sh frontend | |||
More options can be found in [https://github.com/mozilla/balrog-ui/blob/master/README.md ui/README.md] | More options can be found in [https://github.com/mozilla/balrog-ui/blob/master/README.md ui/README.md] | ||