Skip to content

dotnet test mtp lost --artifacts-pathΒ #53204

@afscrome

Description

@afscrome

Describe the bug

dotnet test in MTP mode doesn't support the --artifacts-path option that was supported in VStest mode, and supported by other dotnet commands.

To Reproduce

See the below pipeline. I expect to be able to use --artifacts-path ${{ env.ARTIFACTS_PATH }} on the test command like I could in VS test mode, and like I can on other commands. Instead I have to work around by specifying --p:ArtifactsPath=${{ env.ARTIFACTS_PATH }} instead.

jobs:
  build:
    name: πŸ—οΈ Build and test
    runs-on: ubuntu-latest

    env:
      ARTIFACTS_PATH: ${{ github.workspace }}/blahblahblah/

   steps:
      - name: πŸ“₯ Restore dependencies
        id: restore
        run: dotnet restore --artifacts-path ${{ env.ARTIFACTS_PATH }} -bl:${{ env.BINLOG_PATH }}/restore.binlog

      - name: πŸ—οΈ Build
        id: build
        run: dotnet build --configuration ${{ inputs.configuration }} --no-restore --artifacts-path ${{ env.ARTIFACTS_PATH }} -bl:${{ env.BINLOG_PATH }}/build.binlog

      - name: πŸ§ͺ Test
        id: test
        run: dotnet test --configuration ${{ inputs.configuration }} --no-build --artifacts-path ${{ env.ARTIFACTS_PATH }} -bl:${{ env.BINLOG_PATH }}/test.binlog --output Detailed --results-directory ${{ env.TESTRESULTS_PATH }}

Exceptions (if any)

Further technical details

details of dotnet --info

- The IDE (VS / VS Code/ VS4Mac) you're running on, and its version

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions