Skill

scopy-test-format

Defines Scopy plugin test conventions: UIDs, RBP priorities (P0-P3), RST templates, section sequences, prerequisites. For test case docs and scripts.

testing

documentation

npx claudepluginhub analogdevicesinc/scopy --plugin scopy_dev_plugin

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Format: **`TST.<PLUGIN_UPPER>.<TEST_NAME_UPPER_SNAKE>`**

SKILL.md

Similar Skills

test-automation-quality-checks

493

Validates JS automated test scripts for Scopy plugins using 7 rules: UID-RST matching, API method checks, post-setter sleeps, state restoration, visual patterns, termination, coverage. For js/testAutomations/.

scopy_dev_plugin

test-case-gen

Generates, evaluates, audits, and normalizes QA test cases to RAVN standards. Triggers on requests to create, score, review coverage, or reformat test cases.

16 files1 tool

ravn-ai-toolkit

testing-guide

Provides testing pyramid standards and best practices for UT/IT/ST/E2E tests supporting ISTQB and Industry Pyramid frameworks. Guides writing tests, coverage analysis, strategy, and naming.

3 files

universal-dev-standards

Stats

Parent Repo Stars493

Parent Repo Forks182

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Scopy Test Case Conventions

UID Convention

Format: TST.<PLUGIN_UPPER>.<TEST_NAME_UPPER_SNAKE>

Examples:

TST.AD9371.PLUGIN_LOADS
TST.AD9371.RX_LO_FREQUENCY_READBACK
TST.AD9371.ADVANCED_PANEL_VISIBLE

Rules:

<PLUGIN_UPPER> = plugin folder name uppercased (e.g., ad9371 -> AD9371)
<TEST_NAME> = short descriptive name in UPPER_SNAKE_CASE
UIDs must be unique across all existing test files in scopy/docs/tests/plugins/

RBP Priority Levels

Priority	When to use
P0	Plugin loads test — must be first test, must pass for anything else to matter
P1	Core read/write for primary attributes in each main section
P2	Advanced tab attributes, optional features, secondary settings
P3	Diagnostics, display/cosmetic tests, edge cases, multi-device scenarios

Every plugin must have exactly one P0 test: Plugin Loads.

Standard Test Sequence Per Section

For each tab/section in the plugin, write at minimum:

Section visible (P1) — open plugin, switch to section, verify it is displayed
Key attribute write-readback (P1) — change a value, confirm the hardware reflects it
Refresh (P1) — click the refresh button and confirm displayed values update (only if plugin has a refresh button)

RST Test Entry Template

Test N: <Title>
~~~~~~~~~~~~~~~~~~

**UID:** TST.<PLUGIN>.<TEST_NAME>

**RBP:** P0

**Description:** <One sentence describing what this test verifies.>

**OS:** ANY

**Preconditions:**
    - <Hardware or software requirement>

**Steps:**
    1. <Action step>
        - **Expected result:** <Specific verifiable outcome>
        - **Actual result:**

..
  Actual test result goes here.
..

**Tested OS:**

..
  Details about the tested OS goes here.
..

**Comments:**

..
  Any comments about the test goes here.
..

**Result:** PASS/FAIL

..
  The result of the test goes here (PASS/FAIL).
..

Prerequisites Block (top of test file)

.. _<plugin>_tests:

<Device Name> Test Suite
================================================================================

**Prerequisites:**
    - Scopy vX.Y or later with <Plugin Name> plugin installed
    - <Device name> device connected
    - Device drivers and firmware are up to date
    - Reset .ini files to default by pressing **Reset** button in Preferences

Content Rules

Do NOT fill in Actual result:, Tested OS:, Comments:, or Result: fields
Result: always stays as the literal text PASS/FAIL
Test steps must be action-focused (1-2 sentences each)
Expected results must be verifiable — not vague phrases like "works correctly"
Heading ~~ underlines must be at least as long as the heading text