Dev environement installation
- https://github.com/TiBillet/Lespass
- https://github.com/TiBillet/Fedow
- https://github.com/TiBillet/LaBoutik
- https://github.com/TiBillet/Test-Driven-Development
git clone git@github.com:TiBillet/Test-Driven-Development.git
git clone git@github.com:TiBillet/Lespass.git
git clone git@github.com:TiBillet/LaBoutik.git
git clone git@github.com:TiBillet/Fedow.gitcp env_example .envdocker compose up -d
docker compose logs -f # to see the logsEnter on each django container to start the dev server exemple with Fedow :
# on host :
docker exec -ti fedow_django bash
# inside the containe :
poetry shell # enter the python venv
./flush.sh # to start from scratch with demo/test data
# or
rsp # alias for python manage.py runserver 0.0.0.0:8000, to start the server if you don't want to flushYou have to do the same with : lespass_django and laboutik_django
Flush the 3 container and run ./manage.py test on the laboutik_django container
docker network create frontendVérifier chaque conteneur(Fedow, Lespass, LaBoutik) est bien construit(build) et se lance correctement
docker compose build
docker compose up -d
docker compose downDans la méthode all_tests du fichier ./dev_environment_auto/launch_all_tests; exemple :
echo "- Lancement des test du dossier tests/laboutik/"
docker exec -ti playwright /bin/bash -c "npx playwright test tests/laboutik/"
# ajouter ici vos dossiers de tests / add your test files here
echo "Lancement tests lespass :"
docker exec -ti playwright /bin/bash -c "npx playwright test tests/lespass/"Appliquer la commande "chmod +x" à chaque fichier du dossier ./dev_environment_auto/.
Faire de même pour ./playwright/start_all_tests, ./playwright/start_env et ./playwright/stop_env
cd playwright
# lancement de l'environnement de tests
./start_env
# lance les tests
./start_all_testsdocker system prune -a- Relancer l'étape Test Playwright