Civil CCD Definition and E2E tests
The project is dependent on other Civil repositories:
To set up complete local environment for Civil check civil-sdk
Preview environment will be created when opening new PR. Camunda BPMN definitions will be pulled from the latest GitHub release. Service instance will be running the latest image version deployed to ACR.
To access XUI visit url (make sure that it starts with https, otherwise IDAM won't let you log in):
https://xui-civil-ccd-pr-PR_NUMBER.service.core-compute-preview.internal
To access Camunda visit url (login and password are both admin):
https://camunda-civil-ccd-pr-PR_NUMBER.service.core-compute-preview.internal
Below labels are needed on the PR
"enable_keep_helm" label to retain helm release on preview
"pr-values:enableNotifyEmails" label to be able to send live notifications on the PR
"pr-values:elasticsearch" label to have elastic search running - needed for scheduler testing
"pr-values:enableWA" label to verify work allocation task
Running Crossbrowser tests:
Install saucelabs on local machine
$ yarn test:crossbrowserThe repo uses codeceptjs framework for e2e tests.
To install dependencies enter yarn install.
To run e2e tests enter yarn test in the command line.
To run tests with browser window open set SHOW_BROWSER_WINDOW=true. By default, the browser window is hidden.
To run smoke tests enter yarn test:smoke.
To run functional tests enter yarn test:functional.
For running UI tests, set CCD_UI_TESTS=true
Before running API tests, you will need the SENDGRID_API_KEY environment variable setup and to be running the service locally along with all containers.
To run API tests enter yarn test:api.
set CCD_UI_TESTS=false
- Running a test_name.js
-
Select the .js file containing the tests you want to run and modify its run configuration.
-
Set "Node interpreter" to: [...]\node.exe
-
Set "Node parameters" to: "[...]\civil-ccd-definition\node_modules\codeceptjs\bin\codecept.js" run --debug --verbose
-
Set "Working directory" to: "[...]\civil-ccd-definition"
-
Set JavaScript file to: "[...]\test_name.js"
-
Set "Environment variables" to:
-
S2S_SECRET=[...];ENVIRONMENT=[...];NODE_TLS_REJECT_UNAUTHORIZED=0;SHOW_BROWSER_WINDOW=true
- Running a test from package.json
-
Run > Edit configurations > + > Node.js
-
Set "Node interpreter" to: [...]\node.exe
-
Set "Node parameters" to: "[...]\civil-ccd-definition\node_modules\codeceptjs\bin\codecept.js" run --grep @[test_name] --debug --verbose
-
Set "Working directory" to: "[...]\civil-ccd-definition"
-
Set "Environment variables" to:
-
S2S_SECRET=[...];ENVIRONMENT=[...];NODE_TLS_REJECT_UNAUTHORIZED=0;SHOW_BROWSER_WINDOW=true
- Make sure your git version is at least 2.9 using the
git --versioncommand - Run the following command:
git config --local core.hooksPath .git-config/hooks
Once the above is done, you will be required to follow specific conventions for your commit messages and branch names.
If you violate a convention, the git error message will report clearly the convention you should follow and provide additional information where necessary.
Optional:
-
Install this plugin in Chrome: https://github.com/refined-github/refined-github
It will automatically set the title for new PRs according to the first commit message, so you won't have to change it manually.
Note that it will also alter other behaviours in GitHub. Hopefully these will also be improvements to you.
In case of problems
-
Get in touch with your Technical Lead so that they can get you unblocked
-
If the rare eventuality that the above is not possible, you can disable enforcement of conventions using the following command
git config --local --unset core.hooksPathStill, you shouldn't be doing it so make sure you get in touch with a Technical Lead soon afterwards.
This project is licensed under the MIT License - see the LICENSE file for details
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent