Name: console-tests
Rating: 90.8 (1 reviews)
Author: akash-network

console-tests

Write tests for the akash-network/console monorepo following established team patterns and reviewer expectations. Use this skill whenever you need to write, fix, review, or refactor tests in the console project — including unit tests, functional tests, integration tests, or E2E tests for both frontend (deploy-web) and backend (api, notifications, indexer, provider-proxy). Also trigger when the user mentions 'write tests', 'add tests', 'fix tests', 'test this', 'spec file', or asks about testing patterns in the console codebase. When in doubt about whether to use this skill for a testing task in this repo, USE IT.

1.81x

Quality

86%

Does it follow best practices?

Impact

98%

1.81x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Evaluation results

100%

59%

Write Unit Tests for a Wallet Balance Service

API unit test structure and mocking conventions

Criteria

Without context

With context

setup() at describe bottom

100%

No beforeEach

100%

setup() inline param type

100%

setup() no return type

100%

setup() returns all mocks

100%

Root describe uses .name

100%

mock<T>() for mocks

100%

mockConfigService for config

100%

No module-level mocking

100%

Explicit vitest imports

100%

it() no 'should'

100%

No if in assertions

100%

41%

Write Frontend Tests for a Deployment Status Component and Hook

Frontend DEPENDENCIES pattern and component DI

Criteria

Without context

With context

DEPENDENCIES export used

100%

No vi.mock() module-level calls

50%

100%

MockComponents() used

100%

setup() function pattern

100%

getBy* for presence

100%

queryBy* for absence

100%

renderHook for hooks

100%

Services not in DEPENDENCIES

80%

100%

it() no 'should'

100%

Root describe naming

100%

Explicit vitest imports

100%

95%

31%

Write Functional Tests for the Deployment Lease Upsert Endpoint

Functional test whitebox seeding and nock mocking

Criteria

Without context

With context

Whitebox DB seeding

100%

Blackbox HTTP testing

30%

100%

nock for external mocking

100%

No internal service mocking

60%

100%

Plain HTTP client

12%

100%

Shared DB setup reference

100%

Function-based seeders

100%

Race condition test

100%

One endpoint per test

100%

setup() pattern

37%

it() no 'should'

100%

Repository: akash-network/console
Commit: 609b56d

Evaluated: 6 days ago
Agent: Claude Code
Model: Claude Sonnet 4.6

Table of Contents

Write Unit Tests for a Wallet Balance Service Write Frontend Tests for a Deployment Status Component and Hook Write Functional Tests for the Deployment Lease Upsert Endpoint

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.