AppVeyor: Properly upload JUnit xml test results

Open
  • Is something wrong?
#35 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd

Research direction

The issue points to AppVeyor’s test result upload documentation and says EPICS test results can be converted to JUnit XML, but it names no repository files or tests. Read the AppVeyor configuration and find where EPICS test results are generated or converted; then determine how the XML can be uploaded. Done means AppVeyor displays the uploaded results in its test UI.

Written by the indexing model from the issue text.

Description

enhancement

AppVeyor can show test results in the UI when they are properly uploaded.
(see https://www.appveyor.com/docs/running-tests/#uploading-xml-test-results)

That should be possible for EPICS test results converted to JUnit XML.

Dominant language
Python
Stars
8
Forks
21
Avg merge
13h 50m
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from epics-base/ci-scripts

All issues in epics-base/ci-scripts

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.