jayvdb created this task. Herald added subscribers: pywikibot-bugs-list, Zppix, Aklapper.
TASK DESCRIPTION Currently the CI jobs are emitting only unstructured unit test results, which are difficult to parse and re-use. Some CI engines, such as Circle CI and Jenkins understand structured unit tests results. The two commonly understood structured data formats for unit tests are JUnit XML <http://help.catchsoftware.com/display/ET/JUnit+Format> and Cucumber JSON <https://www.relishapp.com/cucumber/cucumber/docs/formatters/json-output-formatter>. Travis CI does not plan to implement this in the immediate future. https://github.com/travis-ci/travis-ci/issues/239 https://github.com/travis-ci/travis-ci/issues/2992 https://github.com/travis-ci/travis-ci/issues/3042 However, it is still useful for Jenkins, which is run in Gerrit, and it is useful for local developers and tools to check the results. pytest and nose appear to have JUnit XML built in : https://pytest.org/latest/usage.html and http://nose.readthedocs.io/en/latest/plugins/xunit.html Circle CI mentions using https://github.com/django-nose/django-nose for Django. For Cucumber - https://pypi.python.org/pypi/nose-json - https://pypi.python.org/pypi/pytest-json (is it Cucumber compatible?) - https://pypi.python.org/pypi/pytest-bdd has a compatible output ( https://github.com/pytest-dev/pytest-bdd/blob/master/pytest_bdd/cucumber_json.py ) This task is to analyse the two formats, verify that the XML outputs of the builtin plugins are correct and usable, and determine if there is a good reason to use Cucumber instead of the built in XML. TASK DETAIL https://phabricator.wikimedia.org/T135794 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: jayvdb Cc: Aklapper, AbdealiJK, Zppix, jayvdb, pywikibot-bugs-list _______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
