This will make it easier to understand the diff when we move these tests to operate via TemplateList. Despite the verbosity, the only attribute we were actually checking here was the name, as a way of identifying which folders had been returned. Looking at the three tests: 1. The first is checking we can correctly filter all folders that a user can access, which involves appending the names of any parent folders the user doesn't have direct access to. 2. The second is checking the same thing but also that we filter the set of folders to just the children of a parent. 3. The third is just checking the filtering of child folders, without any user filtering or name aggregation applied. I've adapted tests (2) and (3) to make it clearer what is tested, focussing the tests on a specific folder and its contents.
notifications-admin
GOV.UK Notify admin application - https://www.notifications.service.gov.uk/
- Register and manage users
- Create and manage services
- Send batch emails and SMS by uploading a CSV
- Show history of notifications
Setting up
Python version
At the moment we run Python 3.9 in production.
NodeJS & NPM
If you don't have NodeJS on your system, install it with homebrew.
brew install node
nvm is a tool for managing different versions of NodeJS. Follow the guidance on nvm's github repository to install it.
Once installed, run the following to switch to the version of NodeJS for this project. If you don't have that version, it should tell you how to install it.
nvm use
environment.sh
In the root directory of the application, run:
echo "
export NOTIFY_ENVIRONMENT='development'
export FLASK_APP=application.py
export FLASK_ENV=development
export WERKZEUG_DEBUG_PIN=off
"> environment.sh
AWS credentials
To run parts of the app, such as uploading letters, you will need appropriate AWS credentials. See the Wiki for more details.
To run the application
# install dependencies, etc.
make bootstrap
# run the web app
make run-flask
Then visit localhost:6012.
Any Python code changes you make should be picked up automatically in development. If you're developing JavaScript code, run npm run watch to achieve the same.
To test the application
# install dependencies, etc.
make bootstrap
# run all the tests
make test
# continuously run js tests
npm run test-watch
To run a specific JavaScript test, you'll need to copy the full command from package.json.