skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

update-expected-app-size

Retrieve updated-expected-sizes artifacts from Azure DevOps CI and apply them to expected files.

2.9k|576|Updated Apr 20, 2016
Search Tags:#automation#update#tests#azure-devops#ci-artifacts#app-size#dotnet-macios
One-click install
npx skills add https://github.com/dotnet/macios --skill update-expected-app-size
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-expected-app-size
Source: https://github.com/dotnet/macios/tree/main/.github/skills/update-expected-app-size
Command: npx skills add https://github.com/dotnet/macios --skill update-expected-app-size

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you update your repository's known-good app size expectations by pulling updated files from Azure DevOps CI artifacts for the current branch, reducing CI failures due to size test drift.

Core Features & Use Cases

  • Retrieve updated expected size files from CI artifacts for the current PR branch.
  • Apply the updated files to tests/dotnet/UnitTests/expected to align local and CI expectations.
  • Trigger on app size test failures or when artifacts are updated after a PR.

Quick Start

Run the skill to pull and apply the latest updated-expected-sizes artifacts from the current branch's CI build.

Frequently Asked Questions about update-expected-app-size

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

FAQPage Schema
How do I update local app size expectations from Azure DevOps CI artifacts?▼

The skill automates retrieval of updated-expected-sizes artifacts from Azure DevOps CI for your current branch and applies them to tests/dotnet/UnitTests/expected to align local and CI expectations.

Why do app size tests fail in CI and how do I fix the expectation drift?▼

App size tests fail in CI due to size test drift. This skill fixes the drift by pulling updated expected size files from Azure DevOps CI artifacts and applying them to your local repository.

Do I need Azure DevOps access to update expected app size files for my branch?▼

Yes, you need access to Azure DevOps CI artifacts and knowledge of the current branch PR in the macios repository to retrieve and apply the updated expected size files.

What is the best way to sync dotnet macios app size tests with CI artifacts?▼

The best way to sync dotnet macios app size tests is to run this skill, which pulls the latest updated-expected-sizes artifacts from your current branch's CI build and applies them to your local expected directory.

When should I trigger an update for local expected app size files?▼

You should trigger the update when app size tests fail in CI or when artifacts are updated after a PR, ensuring your local expected files match the latest CI artifact data.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
2.9k

macios-ci-failure-inspector

Investigate Azure DevOps CI failures for the dotnet/macios repository.

Official
Advanced
aalmadaaalmada
15

run-unit-tests

Run dotnet test on API Service and analyzer unit test projects.

Community
Basic
dotnetdotnet
2.9k

fix-random-ci-test-failure

Analyze flaky CI test failures in dotnet/macios and generate targeted fixes.

Official
Advanced
mpauloskympaulosky

test-discipline

Enforce same-commit test updates for API and counted-resource changes.

Community
Basic