These are functional integration tests for POMS and the NPO Frontend and Backend API.
This is used to test actual deployments of POMS, the POMS Backend API, and the POMS Frontend API
This is currently split up in 3 modules * a shared module, this contains only code which is shared by the other modules but no actual tests * a selenium module. These are pure frontend tests, and will use a headless browser. This is beging replaced by tests via 'fitnesse' * the other functional tests use API’s only, and e.g. create or change data using the backend api and checks whether those changes arrive correctly in the frontend API. This in many cases also uses java clients which are implemented using the actual domain objects.
TODO: somebody decided that the fitnesse tests also are testing API’s. Now I don’t know any more what is what. This is getting chaotic.
These tests are automatically run every day on a jenkins server (requires login) on the 'dev' environments. At request the tests can also be run on the 'test' environment or even on production.
The tests require a configuration file ${USER.HOME}/conf/npo-functional-tests.properties and the selenium
tests additionally require ${USER.HOME}/conf/npo-browser-tests.properties.
These files must contain the required credentials to be able to run the tests.
Default values can be found in src/main/test/resources of the relevant module.
To test against poms-dev ensure you fill in npo-backend-api.password (for the user: npo-backend-api.user )
Also you need to set your email in the npo-backend-api.errors property.
Note: By default the test environment properties will be used. If you want to change that just specify your own env=[local, dev, prod] property in the file.
If you want to run all tests, you need to check out this including git submodules. One of things which are tests is whether all examples of https://github.com/npo-poms/api/tree/master/examples execute without errors (and for a bunch of them extra checks are implemented)
git clone --recurse-submodules https://github.com/npo-poms/functional-tests.gitWe use lombok to avoid boiler plate code. The maven build is aware of this but your IDE may need help. E.g. for intellij: https://plugins.jetbrains.com/plugin/6317-lombok-plugin
We upgraded to junit 5 for the API functional tests. I tried to do the selenium tests too, but that would be quite cumbersome. We’ll wait for a solution for junit5 #878, which would make it better. Unless plans changes and we’re not going to do it this way at all any more.