Testing the bug filer

This tool can work in conjunction with the MetadataTest tool and UI to test and iterate on both the analysis and bug-filing portions of the pipeline locally, without requiring Watson access, Azure queues or blob storage.

It expects a JSON encoded BugFilerMessage, which can be created with the --json option like so:

dotnet run -p ./tools/MetadataTestTool/ \
    --analysis ./test/TestFiles/WatsonAnalysis/Retail_Xbox.xml  \
    --config ./test/TestFiles/SampleTitleConfiguration.json \
    --metadata ./test/TestFiles/CustomMetadata/WatsonToAzureDevOps.cs --json | \
dotnet run -p ./tools/BugFilerTool/ --config ./test/TestFiles/SampleTitleConfiguration.json

Help

Usage: BugFilerTool [options...]

Options:
  --config <string>      Path to the JSON title configuration. (Required)
  --message <string?>    Path to the JSON BugFilerMessage. (Default: null)

Commands:
  allowedvalues     Display fields with allowed values specified.
  findbug           Finds bugs.
  findcrash         Finds crashes.
  requiredfields    Display required fields.

---

This page was last modified on July 03 2024, 07:45 PM (UTC).