https://github.com/hmcts/div-decree-absolute-frontend

Citizen frontend application for Decree Absolute stage of Divorce
https://github.com/hmcts/div-decree-absolute-frontend

jenkins-cft jenkins-cft-d-i

Last synced: about 1 month ago
JSON representation

Citizen frontend application for Decree Absolute stage of Divorce

• Host: GitHub
• URL: https://github.com/hmcts/div-decree-absolute-frontend
• Owner: hmcts
• License: mit
• Created: 2019-06-04T15:22:29.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2024-09-18T09:16:04.000Z (3 months ago)
• Last Synced: 2024-09-19T11:17:18.270Z (3 months ago)
• Topics: jenkins-cft, jenkins-cft-d-i
• Language: JavaScript
• Homepage: https://www.gov.uk/divorce
• Size: 4.66 MB
• Stars: 2
• Watchers: 22
• Forks: 2
• Open Issues: 8
• Metadata Files:
  • Readme: README.md
  • Contributing: .github/CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Divorce Decree Absolute

## Getting started

#### Install dependencies

```shell

yarn install

```

#### Start application

Run Redis DB using Docker

```shell

docker-compose up redis

```

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

```shell

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)

```shell

yarn mocks

```

#### Test application

```shell

yarn test

```

#### Run Functional tests locally

```shell

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.