Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

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

The EAS has automated routines that send email about new addresses. Run theses routines as part of the testing process.
  1. Begin by confirming that you are a recipient of the Change Notification emails.
    1. See config_notifications.py in /automation/src/config/live/ and check/modify variables devAddressChangeNotificationEmails and/or prodAddressChangeNotificationEmails so that they include your email address.
    2. For environments SF_DEV and SF_QA see the devAddressChangeNotificationEmails variable. For environments SF_PROD and SD_PROD see the prodAddressChangeNotificationEmails variable.
  2. Connect to a Windows automation server (SF_DEV, SF_QA, SF_PROD or SD_PROD) using Microsoft Remote Desktop.
  3. Open 'Command Prompt' and change to the folder containing the change notification script https://bitbucket.org/sfgovdt/eas/src/default/automation/src/job.py
    • C:\apps\eas_automation\automation\src
  4. Run the address_change_report job: 
    1. python job.py --env <environment> --job address_change_report --action EXECUTE --v
    2. Substitute <environment> with one of the relevant environments: SF_DEV, SF_QA, SF_PROD, SD_PROD
  5. Run the address_change_notification job:
    1. python job.py --env <environment> --job address_change_notification --action EXECUTE --v
    2.  Substitute <environment> with one of the relevant environments: SF_DEV, SF_QA, SF_PROD, SD_PROD
  6. Check your email inbox to confirm that the change notifications emails were received.
  7. If applicable, revert any temporary changes to the file config_notifications.py that were made in Step 1.
  • No labels