Skip to content
Back to search

test-framework-architect

MarketplaceWorks with Claude CodeGitHub

A guided skill that walks you through designing and building a test automation framework, one approved phase at a time.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kranmal--test-framework-architect/badge.svg)](/listings/kranmal--test-framework-architect)

HTML

<a href="/listings/kranmal--test-framework-architect"><img src="/api/listings/kranmal--test-framework-architect/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

As a plugin:

claude plugin marketplace add kranmal/test-framework-architect
claude plugin install test-framework-architect@test-framework-architect

Or as a plain skill, copy the skill folder:

mkdir -p ~/.claude/skills
cp -R skills/test-framework-architect ~/.claude/skills/

Use `.claude/skills/` inside a project to scope it to that repo.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 17 lines
  1. {
  2. "name": "test-framework-architect",
  3. "description": "A guided skill that walks you through designing and building a test automation framework, one approved phase at a time.",
  4. "owner": {
  5. "name": "Ketan Ranmal"
  6. },
  7. "plugins": [
  8. {
  9. "name": "test-framework-architect",
  10. "source": "./",
  11. "description": "Guided, approval-gated skill that helps you design and build a production-grade test automation framework in 8 phases.",
  12. "author": {
  13. "name": "Ketan Ranmal"
  14. }
  15. }
  16. ]
  17. }
README.md · README · 107 lines
  1. # Test Framework Architect
  2. A [Claude Code](https://claude.com/claude-code) skill that acts as a senior test automation architect and pair programmer. It guides you through building a production-grade test automation framework **one approved step at a time**: it asks before it assumes, explains trade-offs, and writes runnable code into your repo.
  3. ## What it does
  4. 1. **Intake**: pick-list questions (app type, stack, language, team, OS, CI, integrations, compliance, environments, parallelism, standards, deadline, auth approach). "Not sure" gets a flagged, revisitable default.
  5. 2. **Eight approval-gated phases**:
  6. 1. Requirements document (with Non-Goals)
  7. 2. Tool selection (table with alternatives and trade-offs)
  8. 3. Architecture and design pattern (Mermaid diagram)
  9. 4. Project structure
  10. 5. Core infrastructure: config, fixtures, page object base, two page objects, data layer, reporting, logging
  11. 6. First tests: smoke, data-driven, negative
  12. 7. CI/CD pipeline (PR smoke, regression on merge, artifacts, parallelism)
  13. 8. Maintenance and governance guide
  14. 3. **Final deliverable**: a consolidated `README.md` for your new framework.
  15. Authentication is a first-class choice: real UI login, token login, SSO/MFA test identities, **mocked auth**, or a mix.
  16. ## Install
  17. As a plugin:
  18. ```bash
  19. claude plugin marketplace add kranmal/test-framework-architect
  20. claude plugin install test-framework-architect@test-framework-architect
  21. ```
  22. Or as a plain skill, copy the skill folder:
  23. ```bash
  24. mkdir -p ~/.claude/skills
  25. cp -R skills/test-framework-architect ~/.claude/skills/
  26. ```
  27. Use `.claude/skills/` inside a project to scope it to that repo.
  28. ## Use
  29. In an empty (or existing) test repo, start Claude Code and say:
  30. > Help me build a test automation framework.
  31. Or invoke the skill directly with `/test-framework-architect`. Answer the questions, approve each phase, and the framework is written to your working directory.
  32. ## What a session looks like
  33. Illustrative, abridged flow (your answers drive the choices; exact wording varies):
  34. ```text
  35. You: Help me build a test automation framework.
  36. Claude: Four grouped pick-lists (app and scope, team and environment,
  37. integrations and constraints, standards and authentication).
  38. You choose from the options or pick "Other". "Not sure" applies
  39. a default and flags it REVISITABLE.
  40. Claude: ## Intake summary
  41. | Decision | Answer |
  42. |----------|-------------------|
  43. | App | REST API only |
  44. | Language | TypeScript |
  45. | CI | GitHub Actions |
  46. ...
  47. Claude: ## Phase 1: Requirements document
  48. (one page, with Non-Goals and every REVISITABLE default)
  49. Ready to move to Phase 2? Or would you like to adjust anything?
  50. You: Approve.
  51. ...Phases 2-5 repeat the pattern. Phase 5 is confirmed sub-step by
  52. sub-step. In Phase 6 it writes three tests, runs them, then adds a
  53. deliberate failing test to prove screenshots, traces, JUnit and the
  54. HTML report appear on failure, and deletes it again.
  55. ```
  56. The framework is written into your working directory as you approve each phase, with decisions tracked in `docs/decisions.md`.
  57. ## Repo layout
  58. ```
  59. .claude-plugin/plugin.json plugin manifest
  60. .claude-plugin/marketplace.json marketplace entry for installs
  61. .claude-plugin/icon.png plugin icon
  62. skills/test-framework-architect/SKILL.md operating rules and workflow
  63. skills/test-framework-architect/references/
  64. questions.md intake menus and defaults
  65. phases.md spec for each of the 8 phases
  66. stack-matrix.md tool recommendations by language
  67. ci-github-actions.yml verified CI template
  68. scripts/validate.py repo checks (also run in CI)
  69. .github/workflows/validate.yml CI for this repo
  70. ```
  71. ## Contributing
  72. - Add or adjust intake options in `references/questions.md`.
  73. - Add stacks to `references/stack-matrix.md`.
  74. - Run `python3 scripts/validate.py` (and `claude plugin validate .`) before opening a PR; CI runs the same checks.
  75. - Keep `SKILL.md` short; put detail in `references/`.
  76. - Test changes by running the skill against a scratch repo and completing at least Phases 1-6.
  77. ## License
  78. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.