@axa-ch/pod-ice-kpv-summenmeldung

App KPV Summenmeldung

Dependencies installieren:

npm ci

Entwicklung:

npm start

Release:

npm run build:ci

Das Resultat ist das Directory build. Darin befinden sich alle statischen asssets (html, js, css...) für das Deployment.

Test des Releases:

npm run serve:app

Installing and Using Cypress for automated End-2-End Testing

In the open internet Cypress can be installed with npm i -D cypress.
The post install step of the cypress package tries to download the Cypress application (a binary). This download is blocked by the AXA proxy.

For this reason we have to install Cypress with some more ceremony:

• Download the binary manually here: https://download.cypress.io/desktop
  (the McAfee Web Gateway took 10 min to check the file in my case)
• Copy the file cypress.zip to C:\eplatform\tools\Cypress (the directory mus then contain the cypress.zip)
• run in Windows CMD: set CYPRESS_INSTALL_BINARY=C:\eplatform\tools\Cypress\cypress.zip && npm i cypress --no-save
  (alternatively you can run npm run cypress:install)

The flag --no-save prevents the package to be added to the package.json and package-lock.json. This is not a good practice, but this enables new developer inside AXA to clone the project and successfully run npm install.
The drawback here is that a npm install will remove cypress again ... so you have to re-install it after every npm install.

Running Cypress for Development:

npm start
npm run cypress:open:local

Cypress single run on local machine:

npm start
npm run cypress:run:local

Cypress single run for continuous integration against DEV:

npm run cypress:ci:dev

POD PodIceKpvSummenmeldung

This is a Micro Frontend deployable on the AXA.ch WebHub.

Scripts

To install the pod locally: npm install @axa-ch/pod-ice-kpv-summenmeldung

DEV commands

• npm start start local DEV environment
• npm run build to trigger a ESM build needed for Midgard
• npm run test to run local tests
• npm run release to execute a release to NPM (VERY IMPORTANT: Read How To Release on this document).

How to release

1. update package.json in the "version": "x.x.x" field. Please follow semver best practices

2. run npm run release

3. commit to develop, add git tag containg the same version as in step 1 and push

4. Execute jenkins jobs (build & deploy and if all good: promote) with the version added in point 1

Worth a read

• Midgard
• Checklist for POD devs