Skip to content

[BuildCheck] E2E testing plan #10372

@f-alizada

Description

@f-alizada

Context

The functionality provided by the BuildCheck module is increasing, hence as part of the #10316 we would like to stabilize the behaviour by running the tests (manual) and fixing bugs if appeared during the effort.

Goal

  • Validate that documentation of BuildCheck is aligned with actual implementation.
  • Validate that MSBuild with enabled BuildCheck runs successfully on Dotnet Repositories ( MSBuild including )

Part 1

Steps:

  1. Prepare repro project and validate/confirm that the documentation and actual implementation (main branch) are aligned
  2. In case of finding a bug: Check if it is not reported already if not then please report it :) with the label "Area: BuildCheck"
  3. In case something is not clear in Documentation that is also an issue, please report it.

Categories/Scope/How to s

  • Inbox (built-in) analyzers that run during the build execution.

    • How to:
      • BC0101 - shared-output-path ( Person to contact: jankrivanek)
      • BC0102 - double-writes ( Person to contact: jankrivanek)
      • BC0103 - used-environment-variable ( Person to contact: YuliiaKovalova)
    • Scope: Reproduce the BuildCheck errors on different OS: windows, unix, mac.
  • Custom Analyzers

  • Configuration

  • Tracing

    • Person to contact: maridematte
    • How to: -v:d and times should be at the end of logs
    • Scope:
      • Opt-in reporting of time spent via specific analyzers and infra overall.
  • Replay mode

Part 2

This part contains only of running the MSBuild on existing project with BuildCheck enabled.
Steps:

  1. Choose repository in dotnet
  2. Run the MSBuild with BuildCheck enabled on selected repository

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions