Skip to content

gpsaggese/helpers / .claude/skills/testing.reorder

testing.reorder

Verified

Reorganize test classes and functions to match the order of the tested code

FileKindSize
SKILL.mdskill md1.9 KB
---
description: Reorganize test classes and functions to match the order of the tested code
model: haiku
---

# Goal
- Reorganize the Python test classes and functions in a testing file
  `*/test/test_*.py` to match the order of the functions they test in the
  corresponding source file

# Conventions
- For all the code, follow `.claude/skills/coding.rules.md` and
  `.claude/skills/testing.rules.md`

# Workflow

## Find Test Code
- Find the functions in `<FILENAME>.py` that are tested in
  `test/test_<FILENAME>.py`

## Prepare a Plan
- Prepare a plan that maps:
  - Test classes
  - The functions each class tests
  - The file that contains those functions

### Order the Testing Classes in the Same Order as the Python File
- Reorganize `test/test_<FILENAME>.py` to match the order of the functions declared
  in `<FILENAME>.py`

- E.g., if in a Python `.../file.py`
  ```python
  def test1(...)

  def test2(...)
  ```
  the corresponding `.../test/test_file.py`
  ```python
  class Test_test1(...)

  class Test_test2(...)
  ```

### Preserve Behavior Exactly
- Do not modify functionality, logic, signatures, control flow, side effects, or
  semantics
- The resulting code must behave identically to the original

### Move Code Only
- The refactor must be structural only
- Allowed changes:
  - Reordering functions
  - Adding section headers
  - Renaming internal/private functions consistently
- Disallowed changes:
  - Rewriting logic
  - Simplifying implementations
  - Changing APIs
  - Changing imports unnecessarily
  - Modifying formatting beyond what is required for reorganization

## Implement the Plan
- Implement the plan by moving the code without changing it
- Run the related unit tests to make sure everything works

# Verification
- [ ] Confirm test classes appear in the same order as the functions they test
- [ ] Run the related unit tests and confirm they pass
- [ ] Confirm no logic, signatures, or behavior changed
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall