While setting up the environment afresh, it was observed that the test commands, were giving an error of file not found when used without preceding ./ This was not the case earlier, so added both the options to the setup document to make user aware of both the approaches.
After considering this comment on #130 , it would be better to give the user the complete command of docker-compose exec web ./manage.py test -v 2 -p integration_test*.py --settings=happinesspackets.settings.tsting instead of just ./manage.py test -v 2 -p integration_test*.py --settings=happinesspackets.settings.tsting to make it more clear to users that it needs to be run via exec in the docker container.
2.Why is this change helpful?
This change will avoid users getting stuck on errors, and will also be useful to users who are new to the docker environment.
3.Any specific details to consider?
This can be added to the other setup documents as well.
4.What do you think is the outcome of this change?
A user will be able to setup the environment better, and hopefully without having to look for what steps were missed that resulted in an error.
1.What is a summary of your change?
While setting up the environment afresh, it was observed that the test commands, were giving an error of
file not foundwhen used without preceding./This was not the case earlier, so added both the options to the setup document to make user aware of both the approaches.After considering this comment on #130 , it would be better to give the user the complete command of
docker-compose exec web ./manage.py test -v 2 -p integration_test*.py --settings=happinesspackets.settings.tstinginstead of just./manage.py test -v 2 -p integration_test*.py --settings=happinesspackets.settings.tstingto make it more clear to users that it needs to be run viaexecin the docker container.2.Why is this change helpful?
This change will avoid users getting stuck on errors, and will also be useful to users who are new to the docker environment.
3.Any specific details to consider?
This can be added to the other setup documents as well.
4.What do you think is the outcome of this change?
A user will be able to setup the environment better, and hopefully without having to look for what steps were missed that resulted in an error.