skills.rest
VirtoCommerce
VirtoCommerceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

dotnet-unit-test

Creates failing xUnit regression tests for confirmed Virto Commerce backend bugs.

2|1|Updated May 27, 2025
Search Tags:#test automation#dotnet#regression testing#xunit#virto commerce#backend bugs
One-click install
npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill dotnet-unit-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotnet-unit-test
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/dotnet-unit-test
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill dotnet-unit-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers turn confirmed Virto Commerce backend bugs into reproducible failing xUnit tests, ensuring fixes are validated against an objective red-to-green workflow.

Core Features & Use Cases

  • Bug Reproduction Tests: Creates new xUnit tests from bug reports, root-cause analysis, and existing backend behavior without changing current tests.
  • Test Stack Validation: Inspects test projects, dependencies, repository structure, and build constraints to select compatible testing approaches.
  • Use Case: When a Virto Commerce module has a backend defect, use this Skill to add a focused regression test that fails before the fix and verifies the corrected behavior afterward.

Quick Start

Ask the skill to reproduce the confirmed Virto Commerce backend bug as a new failing xUnit test before implementing the fix.

Frequently Asked Questions about dotnet-unit-test

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

FAQPage Schema
How do I create a failing xUnit regression test for a confirmed backend bug?▼

This skill generates failing xUnit regression tests for confirmed Virto Commerce backend bugs by discovering test projects, validating root causes against existing behavior, and adding new tests without altering current test suites.

When do I need to write a failing test before fixing backend bugs?▼

You need a failing test before fixing backend bugs when applying a red-to-green verification workflow to Virto Commerce modules, ensuring the defect is objectively reproducible and the subsequent code corrects the exact validated behavior.

Does this approach work with existing .NET test infrastructure and mocking patterns?▼

Yes, it requires existing .NET test infrastructure, compatible xUnit and mocking patterns, and scoped test execution, inspecting repository structure and build constraints to select approaches that preserve existing test suites.

What's the best way to reproduce Virto Commerce backend defects without changing current tests?▼

The best way to reproduce Virto Commerce backend defects is by generating focused xUnit tests from bug reports and root-cause analysis, applying them to vc-module or vc-platform fixes while preserving the integrity of existing test suites.

Can I use this for vc-module and vc-platform backend fixes specifically?▼

Yes, it specifically applies to vc-module and vc-platform backend fixes, discovering test projects within those repositories and validating root causes to create scoped regression tests for confirmed defects.

Related Skills

Explore More Software Engineering Skills→
richardnpaulrichardnpaul

csharp-testing

Apply C#/.NET testing patterns with xUnit, FluentAssertions, and mocking frameworks.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
augustsclaugustscl
2

lark-workflow-meeting-summary

Aggregate meeting notes into a structured report using vc search and drive queries.

Community
Intermediate
tiancaiamaotiancaiamao
5

test-driven-development

Enforce a red-green-refactor workflow with failing tests before production code.

Community
Intermediate