Skip to content
TrustedSkillsbeta
Back to all skills

Akka Net Testing Patterns

Checked
aaronontheweb·vlatest·testing·MIT

Helps with testing, patterns as part of testing, debugging, and quality assurance workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aaronontheweb/dotnet-skills --skill akka-net-testing-patterns -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aaronontheweb

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aaronontheweb/dotnet-skills at e426ed93a9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 1,251 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides tools and patterns for writing tests for Akka.NET actors, specifically focusing on unit testing and quality assurance workflows. It offers two primary approaches: Akka.Hosting.TestKit (recommended for most use cases) and the traditional Akka.TestKit. The skill helps with verifying actor interactions, message flows, supervision, lifecycle management, mocking dependencies, cluster sharding behavior, and state recovery in Akka.NET applications.

When to use it

  • Writing unit tests for Akka.NET actors.
  • Testing persistent actors that utilize event sourcing.
  • Verifying how actors interact with each other and the messages they exchange.
  • Testing actor supervision and lifecycle management.
  • Mocking external dependencies within actor tests.
  • When building modern .NET applications using Microsoft.Extensions.DependencyInjection and Akka.Hosting.

Key capabilities

  • Akka.Hosting.TestKit: Provides native dependency injection support for testing, allowing service overrides with fakes.
  • Configuration Parity: Enables the use of the same extension methods in tests as are used in production environments.
  • Type-Safe Actor Registry: Facilitates retrieving actor references in a type-safe manner.
  • Traditional Akka.TestKit: Suitable for contributing to the Akka.NET core library, working with legacy systems, or when dependency injection is not utilized.
  • Reference Materials: Includes example code (examples.md) and guidance on anti-patterns and CI/CD integration (anti-patterns-and-reference.md).

Example prompts

Here are a few examples of how you might instruct an agent using this skill:

  • "Write a unit test for my Akka.NET actor, mocking the database connection."
  • "Show me how to configure Akka.Hosting.TestKit for testing with dependency injection."
  • "Give me an example of verifying message flow between two actors in Akka.NET using the TestKit."

Tips & gotchas

  • NuGet Packages: Requires installing specific NuGet packages, including Akka.Hosting.TestKit, a test framework like xUnit, and FluentAssertions for assertions.
  • Akka.Hosting.TestKit Best Practices: Focus on overriding services in the ConfigureServices() method and configuring actors using ConfigureAkka(). Avoid creating custom base classes; favor method overrides instead.