Divorce Decree Absolute

Getting started

Install dependencies

yarn install

Start application

Run Redis DB using Docker

docker-compose up redis

To start running the application on https://localhost:3000. (Note https not http)

yarn dev

This will create a new endpoint of "/session" where you can view and edit the current session. (Note: each time you login/logout of IDAM the session will be reset)

yarn mocks

Test application

yarn test

Run Functional tests locally

yarn test:functional

Run Functional tests locally against AAT

• Connect to the VPN

• Make a copy of config/example-local-aat.yml as config/local-aat.yml (which is ignored by git)

• Substitute any secret values in local-aat.yml from SCM - Do not add/commit secrets to the example file!

• If you want to point to a PR, modify tests.functional.url accordingly.

• Run NODE_ENV=aat yarn test:functional. This would your tests to pick up the new local-aat.yml.

Running additional tests in the Jenkins PR Pipeline

1. Add one or more appropriate labels to your PR in GitHub. Valid labels are:

• enable_full_functional_tests
• enable_fortify_scan

2. Trigger a build of your PR in Jenkins. Fortify scans will take place asynchronously as part of the Static Checks/Container Build step.

• Check the Blue Ocean view for live monitoring, and review the logs once complete for any issues.
• As Fortify scans execute during the Static Checks/Container Build step, you will need to ensure this is triggered by making a minor change to the PR, such as bumping the chart version.