From scopy_dev_plugin
Defines Scopy plugin test conventions: UIDs, RBP priorities (P0-P3), RST templates, section sequences, prerequisites. For test case docs and scripts.
npx claudepluginhub analogdevicesinc/scopy --plugin scopy_dev_pluginThis skill uses the workspace's default tool permissions.
Format: **`TST.<PLUGIN_UPPER>.<TEST_NAME_UPPER_SNAKE>`**
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/.
Generates, evaluates, audits, and normalizes QA test cases to RAVN standards. Triggers on requests to create, score, review coverage, or reformat test cases.
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.
Share bugs, ideas, or general feedback.
Format: TST.<PLUGIN_UPPER>.<TEST_NAME_UPPER_SNAKE>
Examples:
TST.AD9371.PLUGIN_LOADSTST.AD9371.RX_LO_FREQUENCY_READBACKTST.AD9371.ADVANCED_PANEL_VISIBLERules:
<PLUGIN_UPPER> = plugin folder name uppercased (e.g., ad9371 -> AD9371)<TEST_NAME> = short descriptive name in UPPER_SNAKE_CASEscopy/docs/tests/plugins/| 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.
For each tab/section in the plugin, write at minimum:
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).
..
.. _<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
Actual result:, Tested OS:, Comments:, or Result: fieldsResult: always stays as the literal text PASS/FAIL~~ underlines must be at least as long as the heading text