This repository contains the code used to redesign the existing "Claim Status" application used for New Jersey's Temporary Disability Insurance (TDI) and Family Leave Insurance (FLI), managed by the Department of Labor.
JavaScript scripts are injected onto the existing application and manually update the layout and content for a better user experience. Rather than updating the existing JSP code directly, this will enable frequent testing on dev and deployments to prod without OIM as a dependency, both in terms of infrastructure and bandwidth. See CHANGELOG.md
for list of updates made to production.
The script files are hosted on the beta.nj.gov
domain and automatically pushed from the beta
Github repository. This repository houses the code and tests for developing the scripts, while the beta
repository simply houses the compiled assets that need to be hosted. Note that there is a dev
and prod
hosting of the scripts, which corresponds to the dev and prod (https://secure.dol.state.nj.us/DOL_DABI/) versions of the Claim Status application.
- Clone this
paid-leave-claim-status
repository - Use Node 20
- Run
npm install
to install dependencies - Run
npm run build
to build bundled files - Run
npm test
to run Cypress tests
When you make a change and want to see if everything is working, do the following:
- Edit
.js
file insrc/
directory (edit corresponding Cypress test if relevant) - Run
npm run build
to compile files - Run
npm test
to ensure tests still pass - Open relevant test file in
cypress/fixtures
in browser to ensure change looks okay (edit or add new test file if your scenario is not covered) - After code review, push changes to
dev
branch. This will automatically deploy test files on Github pages under the URL https://newjersey.github.io/paid-leave-claim-status/... These test links can be used to share the view under specific claim scenarios with your team. - After the test links have been reviewed, deploy the changes to the dev site. See instructions below for deployment.
- In
paid-leave-claim-status
repository, create a PR to squash & merge changes fromdev
intoprod
. Note that this change does not directly affect deployment, it is just to keep the change history log up to date. - Clone the
beta
repository in the same local directory where the local files for thepaid-leave-claim-status
repo live. - Use Node 20 and
npm run build
to build latest files into bundle. - Run
npm run prep-deploy-dev
(orprep-deploy-prod
based on intended stage), which should copy the files into the correctbeta
directory - Push files to
main
branch ofbeta
repo, and they will be automatically deployed tobeta.nj.gov
to be referenced by the Claim Status application
Note: The following internal Google Doc has URLs and account credentials to test claim status scenarios live in both development and production.