메뉴
Test case conventions for Scopy plugins including UID format, RBP priorities, RST test entry templates, and standard test sequences. Auto-loads when writing test case documentation or automated test scripts.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | scopy-test-format |
| description | Test case conventions for Scopy plugins including UID format, RBP priorities, RST test entry templates, and standard test sequences. Auto-loads when writing test case documentation or automated test scripts. |
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 textGuidelines for using Context7, web search, and other research tools to find solutions outside the Scopy codebase. Loaded when the task involves unfamiliar technology or external libraries.
Core Scopy architecture knowledge including plugin lifecycle, library dependencies, build system, and key design patterns. Loaded by clarify-task and design-task commands.
How Scopy libraries depend on each other, plugin commonalities, MessageBroker topics, shared widgets, style system flow, and build system relationships. Loaded when determining component interactions or change impact.
Decision trees for common Scopy architectural choices - plugin vs core, tool vs section, widget type selection, sync vs async, GNU Radio vs direct, package organization, and API exposure. Loaded when making design decisions.
Catalog of all Scopy development tools including package generator, testing tools, CI scripts, format/license scripts, and dev plugin commands. Loaded when analyzing what tools exist for a task.
Code patterns and examples for Scopy IIOWidget unit tests. Covers standard helpers, data-driven testing, and complex multi-step scenarios. Auto-loads when creating or reviewing `*_Unit_test.js` files.