ctrf-io / ctrf-io/github-test-reporter

Feat: Support Windows agents

Open
#181 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
TypeScript
Stars
376
Forks
42
PR merge metrics
No merged PRs in 30d

Description

I am trying to use this action but having issues with files not being found when using a pattern such as ${{ github.workspace }}\output\Tests\*.ctrf.json

My workflow looks like this:

    - name: Build
      run: dotnet run --project build/Build.csproj -- --verbosity=Minimal --artifactsDir="${{ github.workspace }}\output"

    - name: Print ctrf files in output
      run: |
        echo "ctrf files in output:"
        dir ${{ github.workspace }}\output\Tests\*.ctrf.json
    
    - name: Publish Test Report
      uses: ctrf-io/github-test-reporter@073c73100796cafcbfdc4722c7fa11c29730439e #v1.0.18
      with:
        report-path: ${{ github.workspace }}\output\Tests\*.ctrf.json
        summary-report: true
        github-report: true
        pull-request: true
        update-comment: true
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      if: always()

The dotnet run step produces files in ${{ github.workspace}}\output\Tests and I've verified that they are there by printing the folder in the run but also uploading as artifacts and they are there with contents.

You can see it in action here: https://github.com/MvvmCross/MvvmCross/pull/4918

And a run here: https://github.com/MvvmCross/MvvmCross/actions/runs/16369990918/job/46255845563#step:9:58

It looks like this:

Image

I've tried report-path set to:

  • ${{ github.workspace }}\output\**\*.ctrf.json
  • ${{ github.workspace }}\output\Tests\*.ctrf.json
  • output\Tests\*.ctrf.json

Nothing seems to be working. This is running on Windows as I have Windows specific targets, so I can't easily test on Linux or macOS agents.

What am I doing wrong here?

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the issue on a Windows GitHub Actions runner with the supplied workflow and each report-path pattern. Inspect the action's report-path handling and path/glob matching behavior. Done means a Windows path such as output\Tests*.ctrf.json finds the generated CTRF files and publishes the report.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.