agentleFS
Sign inStart free
mejbaurbaharmejbaurbahar/software-tester-skills/skills/compatibility-testing/SKILL.md

compatibility-testing

Skill1 starsChanged 52 days agoMITView on GitHub

Use when verifying software compatibility across environments, operating systems, database versions, backward/forward API compatibility, and migration rollback safety.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do existing client apps crash when new optional fields are added to API responses?

    line 19
  2. Very specific:

    Test UP migrations against populated databases (not empty schemas).

    line 22
  3. Very specific:

    Test DOWN migrations (rollback) to ensure instant recovery without data corruption.

    line 23
  4. Very specific:

    Verify non-locking migrations: schema changes (e.g.

    line 24
  5. Very specific:

    Verify test suite passes when upgrading Node.js versions (e.g.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Compatibility & Migration Testing

Overview

Compatibility testing ensures that software functions seamlessly across diverse hardware, operating systems, database engines, browser platforms, and third-party dependencies, as well as across version transitions.

Key Testing Dimensions

  1. Backward & Forward Compatibility:
    • Can client version N talk to server version N-1 and N+1?
    • Do existing client apps crash when new optional fields are added to API responses?
    • Are deprecated endpoints properly supported throughout the documented deprecation grace period?
  2. Database Schema Migrations & Rollback:
    • Test UP migrations against populated databases (not empty schemas).
    • Test DOWN migrations (rollback) to ensure instant recovery without data corruption.
    • Verify non-locking migrations: schema changes (e.g. adding columns, indexes) must not lock production tables (CONCURRENTLY in Postgres).
  3. Runtime & Dependency Upgrades:
    • Verify test suite passes when upgrading Node.js versions (e.g. Node 20 to 22), Python (3.11 to 3.12), or core frameworks.
    • Audit transitive dependency breaking changes via package locks.
  4. Data Export/Import Compatibility:
    • Can data exported from version 1.0 be cleanly imported into version 2.0 without loss?

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free