Functional tests to verify Jagger framework

This chapter is dedicated to the functional testing of the Jagger framework

Jagger project contains two test suits for functional testing

• Configuration and load generation functional tests
• JaaS and Http functional tests

Configuration and load generation functional tests

Test suit contains smoke tests to check that java based Jagger configuration can be used without any exceptions.
Also there are tests to verify that Jagger generates load as specified in appropriate load profile in java configuration.
Test suite is a test, written with use of the Jagger framework
Test project: test/java-builder-tests
Scenario Id: JaggerSmokeTests

To run test:

• Optional: Edit profiles/basic/environment.properties to configure Jagger. Default connection is to local H2 DB. See more information about jagger configuration in the Jagger configuration section
• Optional: Edit test.properties file to configure test.service.endpoints property - single value or comma separated list with path to SUT. You may specify this property later in "start test" step.
• Build Jagger project

  cd {jagger-root-folder}
  mvn clean install

• Start test target

  cd test/test-target/target
  java -jar test-target-{version}-war-exec.jar

• Start test

  cd {jagger-root-folder}/test/java-builder-tests/target/java-builder-tests-{version}-full/
  ./start.sh profiles/basic/environment.properties -Dtest.service.endpoints=http://localhost:8080

JaaS and Http functional tests

Test suite contains smoke test to check JaaS REST API and verify Http support components of the framework.
Test suite is a test, written with use of the Jagger framework
Test project: test/jaas-tests
Scenario Id: ts_JaaSTestSuit

To run test:

• Optional: Edit profiles/basic/environment.properties to configure Jagger. Default connection is to local H2 DB. See more information about jagger configuration in the Jagger configuration section
• Optional: Edit test.properties file to configure jaas.endpoint with path to JaaS SUT.
  You may specify this property later in "start test" step.
• Build Jagger project

  cd {jagger-root-folder}
  mvn clean install

• Edit docker/compose/target/context/docker-compose-with-existing-results-db.yml to configure Jagger DB. Jagger DB should contains information about at least one test session with test contains metrics with both plot data and summary information. For example, DB with results of Configuration and load generation functional tests run may be used.
• Run docker compose.

  cd docker/compose/target/context
  docker-compose -f docker-compose-with-existing-results-db.yml up

• Start test

  cd {jagger-root-folder}/test/jaas-tests/target/jaas-tests-{version}-full/
  ./start.sh profiles/basic/environment.properties -Djaas.endpoint=http://localhost:8088