Currently, the system tests are executed in a separate binary.

The branch attached to this issue shows how to add system tests to ctest. However, this still rely on the systemtest binary and testruner python script to execute the tests.

In a long run, we might want to rewrite the tests to be executed using ctest so that they can take advantage of the unit test monitoring dashboard.

Proposed solution

1. Rewrite the tests into pytest format so that the test can be executed using pytest. Currently, the tests inherit the unittest class but are not written in a way that can be executed by pytest
2. Install the custom libraries for system tests during the build process. There are a few custom libraries that need to be installed in order for the system test to execute.
3. Add a step in the jenkins build step to pull the test data from the remote source.

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs.
Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point.
If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer.
To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.

@cailafinn here is the issue I was talking about

pytest can discover and run unittest tests, we experimented with this at the recent developer meeting, so the first point from the proposed solution above is not needed.