Testing

1. User Interface Testing

This check list seems to catch most bugs. We are not going to automate UI testing because it's not appropriate. The application is not massive and is scheduled to be mature in another 12 months or so. Just be sure to execute all the tests therein which takes about an hour if you are adequately caffeinated and focused.

2. Unit Testing

We have a modest number of python/django unit tests.
We do not have any unit tests for the javascript code.
When to write a test?
Here is when I consider writing a unit test.
When you find a bug, try to write a test that finds it.
If you start the debugger, consider writing a unit test test instead.
This can be expensive and so it is reasonable to debate this point.
Use your judgement.
Often writing a test is super easy and very much helps to prevent regressions.

Running the Unit Tests

From the command line run

https://bitbucket.org/sfgovdt/eas/src/default/web/run_tests.cmd

which goes through the settings.py and calls into

https://bitbucket.org/sfgovdt/eas/src/default/web/test_suites.cmd

3. Testing the Change Notification Emails

1. Connect to relevant server (e.g. SF DEV AUTO).
2. Change to relevant folder containing the change notification scripts `https://bitbucket.org/sfgovdt/eas/src/default/automation/src/job.py` (e.g. cd C:/apps/eas_automation/automation/src).
3. Run address_change_report job: 

   1. python job.py --env SF_DEV --job address_change_report --action EXECUTE --v

4. Run address_change_notification job: 

   1. python job.py --env SF_DEV --job address_change_notification --action EXECUTE --v

5. Confirm emails received. (See config_notifications.py in /automation/src/config to confirm you are a recipient.)