Skip to content

Feature/#32 unit tests

Michelle Weidling requested to merge feature/#32-unit-tests into develop



This MR provides unit tests for all genuine backend/API functions that are in the module tapi.xqm.

Does the result of the MR comply to our "definition of done"?

  • Unit tests passed
  • Code reviewed
  • Acceptance criteria met
  • Functional tests passed
  • Non-Functional requirements met
  • Product Owner accepts the User Story

Use Cases

After every commit, the CI pipeline runs and tells you if your most recent commit has broken the API before deploying it to any server.


Function Documentation

  • Of course I provided all my functions with an appropriate documentation.

Are there parts of the documentation we have to adjust

  • No.


Are we able to test this new feature?

  • Yes, you can test by following these steps:
  1. Visit and
  2. look for the latest job (or any job with 6 stages/circles)
  3. have a look at the test results by clicking on the download icon and selecting "Download test_exist_apps". one test fails and is designed to fail.

Another way would be to build the db according to the README and either run the script tests-runner.xq or call localhost:8080/exist/restxq/trigger-tests in order to run the tests.


  • I added a statement to the CHANGELOG.

Version number

  • I bumped the version number in

Related Tickets


#32 (closed)

/cc Mathias Göbel, Frank Schneider, Michelle Weidling

Edited by Michelle Weidling

Merge request reports