Skip to content

Latest commit

 

History

History
74 lines (59 loc) · 3.36 KB

README.md

File metadata and controls

74 lines (59 loc) · 3.36 KB

Idv Context

Build codecov Codacy Badge BCH compliance Quality Gate Status Technical Debt Coverage Lines of Code Maven Central

Todo

  • Token validation
  • Performance tests in pipeline / nightly build?
  • Add identity data lookup policy?

Useful commands

Gradle

// runs tests and builds code
./gradlew clean build
// runs tests (including integration tests which will be slower) and builds code
./gradlew clean build integrationTest
// runs all tests and builds code and applies rules to clean up code formatting etc
./gradlew clean spotlessApply build integrationTest
// runs all tests as above but also builds application docker image and
// then runs application docker image with dependencies running inside docker
// service will be running on port 8081 by default
./gradlew clean spotlessApply build integrationTest buildImage composeUp
// runs spring application on your local machine on port 8081 by default
// using in memory implementations of dependencies
./gradlew bootRun
// check that dependencies are up to date
./gradlew dependencyUpdates

JMeter

Running performance tests

This command should be run from the parent project directory and requires the service to be up and running, which can be done using either the bootRun or composeUp gradle tasks described above.

mkdir -p app/spring/build/reports/jmeter/html;
rm -rf app/spring/build/reports/jmeter/log/*;
jmeter --nongui \
       --forceDeleteResultFile \
       --addprop app/spring/src/performanceTest/jmeter/online-purchase.properties \
       --testfile app/spring/src/performanceTest/jmeter/online-purchase.jmx \
       --logfile app/spring/build/reports/jmeter/log/online-purchase.jtl \
       --reportatendofloadtests \
       --reportoutputfolder app/spring/build/reports/jmeter/html