Adventure Atlas is an application for publishing your very own backpacking adventures, exploring others backpacking adventures and interact with members of the world!
To run, go to frontend directory and in terminal write npx cypress open
From there go to E2E testing and so on. Enter "specs". These are the tests. From there it should be pretty straight forward.
If any tests fail, either the code is wrong, or the test is wrong, or the test cannot access the component based on the provided "aria-label". The cy.getByLabel
command finds the component with the given aria-label.
Co-authors
- Alex Makassiouk ([email protected])
- Ian Aksum
- Mads Hermansen
The following article has been used for the setup:
-
The setup was done with following variables:
- PC: Macbook Pro 16' 2021 M1 pro with Ventura 13.0.1
- vscode: 1.75.0
- python: 3.10.9
- If no Python
$\rightarrow$ install Python 3 - Check Python version:
- In terminal:
-
python3 --version
orpython --version
- Should be at least Python 3.10
- Install node:
- Check node version:
- In terminal:
node --version
- Should be something like v19.4.0
- Change directory into project with:
cd Documents/backpackerApp
- Change above path to your path on your computer
- Run
pip install pipenv
- Run
pipenv shell
- Run
pipenv install django
- Check Django version
python3 -m django --version
- Should be something like 4.1.6
-
cd backend
-
python3 manage.py runserver
-
In browser, go to localhost:8000/admin
- enter "gruppe59" as username
- enter "gruppe59PU" as password
-
Try localhost:8000/api/routes as well to see stored routes in database
-
To stop server press control + c, but for now let server run
- Note: If server is running: open a new terminal window in VS code with the '+' sign
- in upper backend folder run
pipenv install djangorestframework django-cors-headers
- Make sure your local environment is still active. In terminal the start of line should be "(backpackerApp)". If not running run
pipenv shell
cd frontend
npm install
npm start
- Hopefully welcome to our frontend at localhost:3000 !
- Make sure vscode is running in the virtual environment:
Make a branch for each issue. When finished create merge request in GitLab and request peer reviews from other group members. See the following section for branch name conventions.
First specify if branch is working on a new feature with 'feat' or a 'bug'. Then include a dash and the issue number, and then another dash and the 'branch title' in kebab-case. Should be something like:
feat-31-travelroute-overview-page
bug-31-{name or description}