- Java 21 JDK
- Signature Gateway running in local or remote environment
Modify the file application.properties according to the environment where SiGa is running at. Running in remote environment, it´s necessary to configure valid Client authorization data in TestData.java. More about authorization - Authorization.
If you are running SiGa in local docker-compose setup as described at https://github.com/open-eid/SiGa#running-siga-with-docker, then the default configuration should work.
Descriptions of parameters in application.properties:
| Parameter | Example | Description |
|---|---|---|
| siga.application-context-path | /siga-webapp-2.0.1 |
Custom service context. |
| siga.hostname | localhost |
Service URL. |
| siga.port | 8443 |
Service port. |
| siga.protocol | https |
Service protocol. |
| siga.profiles.active | datafileContainer,smartId,mobileId |
Define what profile tests to run. |
| test-files-directory | src/test/resources/ |
Test files directory path. |
| rest-assured-console-logging | false |
Enable RestAssured request/response console logging filters. |
NB! MonitoringT tests do not pass locally as SIVA status is always DOWN.
Run tests
./mvnw clean verifyPS! Groovy and Scala tests do not run automatically.
- At first, generate dynamic classes from WADL and XSD.
./mvnw clean compile- Open this project in IntelliJ (community version will do)
- Open File -> Project Structure
- In the view:
- Make sure Project -> SDK points to Java 21
- Open
*T.javaor*Spec.groovyfile and JUnit Run option should be displayed.
For a report, Allure is required (instructions for download).
After running the tests, you can serve locally Allure report:
allure serve ./target/allure-results/