Results for “unit”

Complete guide for upgrading xUnit 2.9.x to 3.x. Use when upgrading xUnit v2 to v3 or understanding xUnit v3 new features and breaking changes. Covers package updates, async void fixes, IAsyncLifetime adjustments. Includes new features: Assert.Skip, Explicit Tests, Matrix Theory, Assembly Fixtures. Keywords: xunit upgrade, xunit v3, xunit 3.x, xunit migration, xunit upgrade, xunit.v3, OutputType Exe, IAsyncLifetime v3, Assert.Skip, SkipUnless, SkipWhen, Explicit attribute, MatrixTheoryData, AssemblyFixture, breaking changes

The English summary is being prepared. Showing the original description.

Build Laravel features test first with PHPUnit or Pest. Create tests for models, HTTP endpoints, authentication, and permissions, simulate external services, and measure coverage to see which code your tests exercise.

• Building Laravel features test first
• Testing API authentication and permissions
• Simulating payments, mail, and queues in tests

Check physical units, propagate measurement uncertainty through calculations, and format results with meaningful precision. Local tools also inspect Python code for unit and uncertainty mistakes and assess whether calculated magnitudes are physically plausible.

• Convert units while carrying measurement uncertainty
• Build an uncertainty budget from calibration data
• Audit Python calculations for unit and uncertainty errors

Write and update Handsontable unit tests with Jest and type tests with TypeScript. Explains file placement, focused test runs, boundary cases, and checks for public types, while helping choose between isolated logic tests and browser tests.

• Adding unit tests for calculations and data transformations
• Covering bug fixes and internal refactoring
• Checking TypeScript declarations and public exports

Implement rewarded ads with the Google Mobile Ads SDK on Android, iOS, or Unity. Add a user interface for choosing to view an ad for a reward, and follow steps for loading, event handling, display, and verification.

• Add ads users choose to view for in-app rewards
• Implement rewarded ads on Android or iOS
• Integrate rewarded ads into a Unity app

Implement full-screen ads at natural transitions in mobile apps using the Google Mobile Ads SDK. Follow platform-specific guidance for Android, iOS, or Unity, covering ad loading, event handling, display, and implementation verification.

• Add full-screen ads between app screens
• Implement interstitial ads on Android or iOS
• Integrate interstitial ads into a Unity app

Build AI agents in Unity with PuerTsAgent by organizing role instructions, skills loaded when needed, and executable helper modules. The guide covers resource folders, module design, and TypeScript or JavaScript implementation.

• Build an AI assistant for the Unity Editor
• Define a maze exploration agent's behavior
• Separate occasional knowledge into skills

Create English and Chinese changelogs for PuerTS releases on Unity or Unreal. Review platform-specific Git commits, investigate unclear changes, and summarize their impact on users using each platform’s required format.

• Preparing a Unity release changelog
• Preparing an Unreal release changelog
• Updating English and Chinese changelogs together

Choose and optionally run .NET test commands that match the project's SDK, test platform, and framework. Target specific tests, collect reports or diagnostics, and report execution results using syntax appropriate to the repository.

• Getting an exact test command for a repository
• Running a specific class, category, or target framework
• Collecting TRX reports, coverage, or diagnostic logs

Use RQL, a language that chains search and editing steps, to inspect and change Unity Editor content. Find objects, summarize data, update properties, and manage scenes, prefabs, assets, selection, and Play Mode.

• Find scene objects and summarize their properties
• Update lighting or object settings in bulk
• Create and manage scenes, prefabs, and assets

Enable or disable named MCP tools, the tools available to an AI agent, in Unity. Submit several changes together, receive a success result for each name, and optionally inspect operation logs. Settings are saved only when a state changes.

• Enabling several tools together
• Disabling tools for the current task
• Checking results for each requested change

Search Unity's package registry and installed packages by name, ID, or description. Review available versions and installation status before adding a package, using cached results or online lookups for exact matches.

• Finding a package by part of its name
• Searching descriptions for rendering packages
• Checking available versions and installation status

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest attributes, Xunit.SkippableFact, xunit.abstractions/extensibility consolidation, and Xunit.Combinatorial/StaFact compatibility. Do not use for framework conversion or a runner-only migration. For xUnit v3 MTP filter syntax, also use migrate-vstest-to-mtp.

The English summary is being prepared. Showing the original description.

Convert .NET tests from NUnit 3/4 to MSTest v4 while preserving VSTest or MTP. Use for replacing NUnit/NUnit3TestAdapter packages, Test/TestCase/ TestCaseSource/Values attributes, constraint assertions, SetUp/TearDown, OneTimeSetUp, SetUpFixture, FixtureLifeCycle, TestContext, categories, retries, timeouts, and NUnit parallelization. Also use when a "convert NUnit to MSTest" request may already be migrated: inspect and report the no-op. Do not use for NUnit version upgrades, xUnit/TUnit conversion, MSTest upgrades, or runner-only VSTest-to-MTP migration.

The English summary is being prepared. Showing the original description.

Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test profiles, and @TestConfiguration. For framework-agnostic Java use @131-java-testing-unit-testing. For integration tests use @322-frameworks-spring-boot-testing-integration-tests. This should trigger for requests such as Review Java code for Spring Boot unit tests; Apply best practices for Spring Boot unit tests in Java code; Write Mockito-first unit tests for Spring Boot services; Avoid unnecessary @SpringBootTest in Spring unit tests; Review Spring Boot slice-free unit test design. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

Use when you need to review, improve, or write Java unit tests — including migrating from JUnit 4 to JUnit 5, adopting AssertJ for fluent assertions, structuring tests with Given-When-Then, ensuring test independence, applying parameterized tests, mocking dependencies with Mockito, verifying boundary conditions (RIGHT-BICEP, CORRECT, A-TRIP), leveraging JSpecify null-safety annotations, or eliminating testing anti-patterns such as reflection-based tests or shared mutable state. This should trigger for requests such as Review Java code for unit tests; Apply best practices for unit tests in Java code; Write fast JUnit unit tests for Java code; Improve Mockito-based Java unit tests; Refactor Java tests to isolate collaborators. Part of Plinth Toolkit

The English summary is being prepared. Showing the original description.

Your most loyal users aren't just customers - they're potential advocates, contributors, and community members who can become the engine of your growth. Community-led growth isn't about broadcasting to an audience - it's about creating a space where your users connect with each other, share knowledge, and become invested in your success. This skill covers community strategy, platform selection, engagement tactics, ambassador programs, and the metrics that matter. Whether you're building a Discord for developers or a forum for power users, the goal is the same: creating genuine value that makes members want to stay and contribute. Use when "community, discord, forum, user group, ambassador, champions, developer relations, devrel, community engagement, community growth, power users, superfans, community, discord, engagement, devrel, ambassador, forum, user-community, growth, retention, champions" mentioned.

The English summary is being prepared. Showing the original description.

Set up and run kube-bench to check Kubernetes configuration against CIS security benchmarks. Select the appropriate benchmark and cluster components, then export JSON or JUnit results for automated pipelines and troubleshoot skipped checks or incorrect detection.

• Setting up kube-bench for the first time
• Selecting benchmark versions and scan targets
• Exporting JSON or JUnit results for CI

Add Google Mobile Ads banners to Android, iOS, or Unity apps. Guides implementation from defining the ad view and choosing its size to handling load events, loading the banner, and checking the completed integration.

• Add a banner ad to an Android app
• Place an adaptive banner at the top or bottom of an iOS app
• Integrate a banner ad into a Unity app

Identify a .NET project’s test framework, project format, and execution platform: VSTest or Microsoft.Testing.Platform. Trace configuration imports and overrides to explain the result, including conflicting settings or differences between target frameworks.

• Determine whether tests execute on VSTest or MTP
• Identify the test framework from project configuration
• Investigate conflicting runner settings

Inspect available RQL data sources and component types in loaded Unity scenes, including counts. Provide a type name to see its fields, properties, and methods before writing a query.

• Inspect component types in loaded scenes
• Check available members on an unfamiliar type
• Identify read-only members before editing

Run Unity tests in EditMode or PlayMode, selecting specific assemblies, namespaces, classes or methods. Review individual outcomes and durations, filter results, and include failure messages, logs or stack traces to investigate problems.

• Rerun a specific test class after changes
• Run tests in EditMode or PlayMode
• Review only failed test results

List packages installed in a Unity project with their names, versions, sources, and descriptions. Filter by source or keyword, or show only direct dependencies—the packages explicitly listed in the project manifest.

• Checking installed package versions
• Listing packages installed from Git
• Reviewing only direct dependencies

Build unity-mcp-cli from its TypeScript source and optionally make the command available across terminals with npm link. Covers dependency installation, compilation, version checks, and reporting errors when a step fails.

• Build unity-mcp-cli from source for the first time
• Rebuild the CLI after changing TypeScript files
• Make the CLI command available across terminals