一键在 Manus 中运行任何 Skill

开始使用

writing-tests

星标17

分支2

更新时间2026年4月26日 11:19

Use before writing, adding, or modifying any test in blotztask-test/.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

sol-wizard

sol-wizard/Blotz-Task-App

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Writing Tests

Step 1 — Is this test necessary?

Make your own judgment first: does this code contain non-obvious logic that could break silently, and does the test actually bring value to the project — or is it unnecessary?

If yes, proceed.
If no, do not refuse outright. Share your reasoning and let the dev respond. Write the test only if their response genuinely changes your judgment; then proceed.

Step 2 — If it's necessary, follow these conventions

Framework: xUnit + FluentAssertions + Testcontainers.MsSql. Run with cd blotztask-test && dotnet test.
Naming: Handle_<Scenario>_<ExpectedOutcome> inside a <Subject>Tests class.
Structure: AAA with inline // Arrange / // Act / // Assert comments. Seed data via DataSeeder — never depend on existing DB state.
No mocking: tests run against a real SQL Server container via DatabaseFixture.
Assertions: always include because: — it documents the rule. spl

result.Should().HaveCount(3, because: "only tasks within the UTC window are returned");

同仓库更多 Skills

同仓库

create-pr

sol-wizard/Blotz-Task-App

Use when the user wants to open a pull request — e.g. "create me a PR", "open a PR", "raise a PR" — or wants to fix the description or release note on an existing PR.

2026-07-2117

private-context

sol-wizard/Blotz-Task-App

Use when starting feature work, making design/product decisions, or needing the rationale or history behind a feature — checks the private companion repo for planning notes and decision records.

2026-06-1017

working-with-ai-agent

sol-wizard/Blotz-Task-App

Use when the developer is implementing, modifying, or fixing any AI feature in this project

2026-06-1017

create-blotz-pbi

sol-wizard/Blotz-Task-App

Use when the user wants to capture an idea, problem, or task as a PBI in the Blotz backlog — e.g. "create a PBI for this", "add this to the backlog".

2026-06-0817

backend-changes

sol-wizard/Blotz-Task-App

Use when the developer is adding, modifying, or fixing backend API logic — endpoints, handlers, domain entities, events, or anything in `blotztask-api/`.

2026-04-2617

database-migrations

sol-wizard/Blotz-Task-App

Use when the developer is adding, renaming, or changing a database field, entity, or relationship — anything that produces an EF Core migration.

2026-04-2617

name	writing-tests
description	Use before writing, adding, or modifying any test in blotztask-test/.

Writing Tests

Step 1 — Is this test necessary?

Make your own judgment first: does this code contain non-obvious logic that could break silently, and does the test actually bring value to the project — or is it unnecessary?

If yes, proceed.
If no, do not refuse outright. Share your reasoning and let the dev respond. Write the test only if their response genuinely changes your judgment; then proceed.

Step 2 — If it's necessary, follow these conventions

Framework: xUnit + FluentAssertions + Testcontainers.MsSql. Run with cd blotztask-test && dotnet test.
Naming: Handle_<Scenario>_<ExpectedOutcome> inside a <Subject>Tests class.
Structure: AAA with inline // Arrange / // Act / // Assert comments. Seed data via DataSeeder — never depend on existing DB state.
No mocking: tests run against a real SQL Server container via DatabaseFixture.
Assertions: always include because: — it documents the rule. spl

result.Should().HaveCount(3, because: "only tasks within the UTC window are returned");