https://github.com/dvsa/cvs-auto-svc
CVS Services Automated regression pack
https://github.com/dvsa/cvs-auto-svc
app-dev cvs-project
Last synced: 8 months ago
JSON representation
CVS Services Automated regression pack
- Host: GitHub
- URL: https://github.com/dvsa/cvs-auto-svc
- Owner: dvsa
- License: mit
- Created: 2018-12-20T11:49:42.000Z (over 7 years ago)
- Default Branch: develop
- Last Pushed: 2024-10-24T10:14:33.000Z (over 1 year ago)
- Last Synced: 2024-10-25T02:39:57.530Z (over 1 year ago)
- Topics: app-dev, cvs-project
- Language: Java
- Homepage:
- Size: 2.41 MB
- Stars: 4
- Watchers: 14
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# cvs-auto-svc
This is the the project for creating and managing the backend services automated tests
## Getting Started
These instructions will get you up and running with the automation framework.
### Prerequisites
- Browserstack credentials
- Jenkins access
- Java 1.8 and above
- Maven
- Git
- NodeJs
- IntelliJ
### Setting Up
#### Git Hooks
Please set up the following prepush git hook in .git/hooks/pre-push
```
#!/bin/sh
npm run prepush && git log -p | scanrepo
```
##### Security
Please install and run the following securiy programs as part of your testing process:
https://github.com/awslabs/git-secrets
- After installing, do a one-time set up with `git secrets --register-aws`. Run with `git secrets --scan`.
https://github.com/UKHomeOffice/repo-security-scanner
- After installing, run with `git log -p | scanrepo`.
These will be run as part of prepush so please make sure you set up the git hook above so you don't accidentally introduce any new security vulnerabilities.
#### Config File
In the project structure create the file: `cvs-auto-svc/src/main/resources/conf/environment.properties`
(Do NOT add it to Git versioning !)
The file should contain:
```properties
base.path.url=
no.data.base.path.url=
s3.bucket="cvs-cert-develop"
branch.name=
microsoftonline.url=https://login.microsoftonline.com//oauth2/authorize?client_id=&response_type=id_token&redirect_uri=http://localhost:3000&scope=openid&response_mode=fragment&nonce=678910
microsoftonline.username=
microsoftonline.pass=
microsoftonline.url.v2=https://login.microsoftonline.com//oauth2/v2.0/authorize?client_id=&response_type=id_token&scope=openid &redirect_uri=http://localhost:8100&nonce=12345
microsoftonline.username.v2=
microsoftonline.pass.v2=
browserstack.username=
browserstack.password=
data.location=develop
api.keys=
app.token.url=https://login.microsoftonline.com//oauth2/v2.0/token
app.client.id=
app.scope=
app.client.secret=
```
## Running locally
Running can be triggered from IntelliJ or via mvn command in the terminal
## Running in CI
In Jenkins tests may be executed against either a branch or develop:
- [UPDATE__BRANCH](https://jenkins.cvs.dvsacloud.uk/job/UPDATE__BRANCH/job/job_feature_test_backend/)
- [UPDATE__DEVELOP](https://jenkins.cvs.dvsacloud.uk/job/UPDATE__DEVELOP/job/job_develop_test_backend/)
Execution is triggered via "Build with Parameters" job with the options to select the test group from the 'MVN_TAG' dropdown.
A full data reseed is also optional via a checkbox (selected by default)
## Contributors
- Bogdan Catalin Florea - @bflorea
- Dragos Panzaru - @dpanzaru
- Deepika Singh - @deepikasingh