AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Test Patterns

skill-weisser-dev-awesome-opencode-test-patterns · by weisser-dev

Generate tests following project conventions with proper patterns for unit, integration, and e2e testing

No reviews yet
0 installs
55 views
0.0% view→install

Install

$ agentstack add skill-weisser-dev-awesome-opencode-test-patterns

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-weisser-dev-awesome-opencode-test-patterns)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Test Patterns? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

What I do

  • Analyze existing test patterns in the project
  • Generate tests that follow the same style and conventions
  • Cover happy paths, edge cases, and error scenarios
  • Use the project's testing framework and utilities

When to use me

Use this skill when you need to write tests for new or existing code. This skill first analyzes existing tests to match the project's style.

Process

  1. Discover: Find existing tests to understand patterns
  • Look for *.test.*, *.spec.*, __tests__/ directories
  • Identify testing framework (Jest, Vitest, Pytest, JUnit, etc.)
  • Note assertion style, mock patterns, and setup/teardown
  1. Analyze: Read the code under test
  • Identify public API surface
  • Find branching logic and edge cases
  • Note dependencies that need mocking
  1. Generate: Write tests following discovered patterns

Test Patterns by Framework

JavaScript/TypeScript (Vitest/Jest)

describe("ModuleName", () => {
  // Setup
  beforeEach(() => { /* ... */ })

  describe("methodName", () => {
    it("should return expected value for valid input", () => {
      // Arrange
      const input = createTestInput()
      // Act
      const result = methodName(input)
      // Assert
      expect(result).toEqual(expectedValue)
    })

    it("should throw for invalid input", () => {
      expect(() => methodName(null)).toThrow(ExpectedError)
    })
  })
})

Python (Pytest)

class TestModuleName:
    @pytest.fixture
    def setup(self):
        return create_test_fixture()

    def test_method_returns_expected_for_valid_input(self, setup):
        result = method_name(setup)
        assert result == expected_value

    def test_method_raises_for_invalid_input(self):
        with pytest.raises(ExpectedError):
            method_name(None)

Java (JUnit 5)

@DisplayName("ModuleName Tests")
class ModuleNameTest {
    @BeforeEach
    void setUp() { /* ... */ }

    @Test
    @DisplayName("should return expected value for valid input")
    void methodName_validInput_returnsExpected() {
        var result = moduleName.methodName(validInput);
        assertEquals(expected, result);
    }

    @Test
    @DisplayName("should throw for invalid input")
    void methodName_invalidInput_throws() {
        assertThrows(ExpectedException.class,
            () -> moduleName.methodName(null));
    }
}

Coverage Targets

  • Unit Tests: Every public method, all branches
  • Edge Cases: Null/empty, boundary values, large inputs
  • Error Paths: Invalid input, network failures, timeouts
  • Integration: Key workflows between components

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.