test-arcade

Build the Arcade SDK locally and validate it against a test repository.

13|20|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/arcade-skills --skill test-arcade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-arcade
Source: https://github.com/dotnet/arcade-skills/tree/main/plugins/dotnet-dnceng/skills/test-arcade
Command: npx skills add https://github.com/dotnet/arcade-skills --skill test-arcade

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pwsh, dotnet, git, and includes scripts (resource) components.

What problem does it solve?

Build the Arcade SDK from a local checkout, publish the artifacts to a local NuGet feed, and validate by building a test repository against those packages.

Use this skill when testing local Arcade changes against a consuming repo, validating Arcade SDK changes before merging, or verifying that a repo can build with a new Arcade version.

Core Features & Use Cases

  • End-to-end local Arcade build workflow: from local checkout to local NuGet feed creation and test repo validation.
  • Local feed configuration and test repo alignment: updates NuGet.config and global.json to point to locally-built Arcade packages.
  • Optional SigningValidation (SignCheck) for validating artifact signatures.

Quick Start

Run pwsh ./scripts/Test-Arcade.ps1 -Arcade /path/to/arcade -TestRepo /path/to/test-repo to build Arcade locally and validate against a test repo.

Frequently Asked Questions about test-arcade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build the Arcade SDK locally and validate it against a test repository?

Yes, PowerShell 7+ is required to build and validate the Arcade SDK locally. The workflow also requires Git and the .NET SDK installed to properly configure the local NuGet feed and run the test repository build.

How does a local NuGet feed validate Arcade SDK changes?

A local NuGet feed validates Arcade SDK changes by hosting the locally built artifacts. The workflow updates the test repository's NuGet.config and global.json to point to this feed, ensuring the repo builds against your local Arcade version.

Can I run SigningValidation on test repository build output?

Yes, you can optionally run SigningValidation (SignCheck) on the test repository build output. This validates artifact signatures during the Arcade SDK local build and test repo validation workflow to ensure package integrity.

What is the best way to test local Arcade changes against a consuming repo?

The best way to test local Arcade changes against a consuming repo is automating the end-to-end workflow: build Arcade from your local checkout, publish to a local NuGet feed, update the test repo's configuration, and build the test repo against those packages.

Why does my test repository not build with a locally built Arcade version?

A test repository may not build with a locally built Arcade version if the NuGet.config and global.json are not updated to point to the local feed. The Arcade validation workflow automates these configuration updates to ensure proper package resolution.