Skip to content

Move beekeepers tests to seperate CI job.

Wieslaw Kedzierski requested to merge 69-seperate-job-for-bk-tests into develop

Closes #69 (closed)

This MR added a dedicated job for beekeeper test.

It separates it by using test_beekeeper prefix in test names and by using -k [not] test_beekeeper.

Maybe it would be better to use @pytest.mark.beekeeper instead of the pattern name?

The current solution touches only the newly created test /commandline /api_test , maybe former tests regarding beekeeper should be renamed (marked) as well?

@mzebrak @kmochocki what do you guys think?

Test coverage: all :

pytest --collect-only tests/ 
470 tests collected in 2.89s

clive

pytest -k "not test_autocompletion_time and not test_beekeeper" -n auto --durations 0 --junitxml=report.xml tests/ --collect-only
300/470 tests collected (170 deselected) in 2.85s
pytest -k "test_autocompletion_time" --durations 0 --junitxml=report.xml tests/ --collect-only
1/470 tests collected (469 deselected) in 2.75s|

beekeepers:

pytest -k "test_beekeeper" -n auto --durations 0 --junitxml=report.xml tests/
169/470 tests collected (301 deselected) in 2.75s

300 + 1 + 169 = 470 - so all are executed.

Merge request reports