sumo-qa 0.1.0__tar.gz

sumo_qa-0.1.0/.claude-plugin/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "sumo-qa-dev",
+  "description": "Self-hosted marketplace for the sumo-qa skills library + MCP server.",
+  "owner": {
+    "name": "Sumith Ramsookbhai",
+    "email": "sumithr51@gmail.com"
+  },
+  "plugins": [
+    {
+      "name": "sumo-qa",
+      "description": "Senior-QA-shaped MCP server + skills library: pre-coding QA planning, TDD scaffolding, mutation-testing follow-up, code review, test-data discovery.",
+      "version": "0.1.0",
+      "source": "./",
+      "author": {
+        "name": "Sumith Ramsookbhai",
+        "email": "sumithr51@gmail.com"
+      }
+    }
+  ]
+}

sumo_qa-0.1.0/.claude-plugin/plugin.json

@@ -0,0 +1,22 @@
+{
+  "name": "sumo-qa",
+  "description": "Senior-QA-shaped MCP server + skills library: pre-coding QA planning, TDD scaffolding, mutation-testing follow-up, code review, test-data discovery. Iron-Law-enforced workflows for deciding approach, prepping for work, TDD-scaffolding, reviewing diffs, strengthening tests, and repo-wide strategising.",
+  "version": "0.1.0",
+  "author": {
+    "name": "Sumith Ramsookbhai",
+    "email": "sumithr51@gmail.com"
+  },
+  "homepage": "https://github.com/sumithr/sumo-qa",
+  "repository": "https://github.com/sumithr/sumo-qa",
+  "license": "Apache-2.0",
+  "keywords": [
+    "qa",
+    "testing",
+    "tdd",
+    "mutation-testing",
+    "code-review",
+    "istqb",
+    "senior-qa",
+    "test-data"
+  ]
+}

sumo_qa-0.1.0/.codex-plugin/plugin.json

@@ -0,0 +1,43 @@
+{
+  "name": "sumo-qa",
+  "version": "0.1.0",
+  "description": "Senior-QA skills library + MCP server: pre-coding QA planning, TDD scaffolding, mutation-testing follow-up, code review, repo-wide QA strategy, and test-data discovery.",
+  "author": {
+    "name": "Sumith Ramsookbhai",
+    "email": "sumithr51@gmail.com",
+    "url": "https://github.com/SumithRamsookbhai"
+  },
+  "homepage": "https://github.com/sumithr/sumo-qa",
+  "repository": "https://github.com/sumithr/sumo-qa",
+  "license": "Apache-2.0",
+  "keywords": [
+    "qa",
+    "testing",
+    "tdd",
+    "mutation-testing",
+    "code-review",
+    "istqb",
+    "senior-qa",
+    "test-data"
+  ],
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "Sumo QA",
+    "shortDescription": "Senior-QA workflows: pre-coding QA planning, TDD, mutation-testing follow-up, code review, test-data discovery.",
+    "longDescription": "Use Sumo QA to drive software changes through a disciplined senior-QA workflow: pick the right approach for the change shape, name risks anchored in code, scaffold red tests before production code, strengthen weak assertions against mutation survivors, review diffs with fresh verification evidence, and find or register known-good test data \u2014 all grounded in ISTQB principles, change classifications, and the team's loaded standards.",
+    "developerName": "Sumith Ramsookbhai",
+    "category": "Coding",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "defaultPrompt": [
+      "Plan QA for this story before I start coding.",
+      "Review my changes for risk before I merge.",
+      "Audit our test coverage and design a QA strategy.",
+      "Find me a known-good test data record for this scenario."
+    ],
+    "websiteURL": "https://github.com/sumithr/sumo-qa"
+  }
+}

sumo_qa-0.1.0/.cursor-plugin/plugin.json

@@ -0,0 +1,25 @@
+{
+  "name": "sumo-qa",
+  "displayName": "Sumo QA",
+  "description": "Senior-QA skills library + MCP server: pre-coding QA planning, TDD scaffolding, mutation-testing follow-up, code review, test-data discovery.",
+  "version": "0.1.0",
+  "author": {
+    "name": "Sumith Ramsookbhai",
+    "email": "sumithr51@gmail.com"
+  },
+  "homepage": "https://github.com/sumithr/sumo-qa",
+  "repository": "https://github.com/sumithr/sumo-qa",
+  "license": "Apache-2.0",
+  "keywords": [
+    "qa",
+    "testing",
+    "tdd",
+    "mutation-testing",
+    "code-review",
+    "istqb",
+    "senior-qa",
+    "test-data"
+  ],
+  "skills": "./skills/",
+  "hooks": "./hooks/hooks-cursor.json"
+}

sumo_qa-0.1.0/.dockerignore

@@ -0,0 +1,13 @@
+.git
+.venv
+__pycache__
+*.py[cod]
+*.egg-info
+.coverage
+.pytest_cache
+.ruff_cache
+.mypy_cache
+.DS_Store
+.env
+dist
+build

sumo_qa-0.1.0/.github/copilot-instructions.md

@@ -0,0 +1,24 @@
+# QA tasks via sumo-qa MCP
+
+For QA-shaped requests in this repo (test plans, code review, scaffolding
+tests, finding test data, deciding QA approach), fetch the relevant prompt
+from the `sumo-qa` MCP and follow its checklist.
+
+Available skills (each registered as an MCP prompt with the same name,
+hyphens replaced by underscores):
+
+- `using_sumo_qa` — entry router; load this first for any QA intent
+- `qa_deciding_approach` — pick the QA approach for the work
+- `qa_preparing_for_work` — plan QA before coding starts
+- `qa_creating_test_plan` — produce entry/exit criteria, phases, deliverables
+- `qa_implementing_with_tdd` — red-green-refactor cycle
+- `qa_reviewing_before_merge` — review local diff
+- `qa_strengthening_tests` — mutation-testing follow-up
+- `qa_finding_test_data` — known-good test data discovery and validation
+- `qa_answering_testing_question` — generic "how do I test this?"
+- `sumo_qa_strategising` — repo-wide QA strategy
+
+The skills carry the senior-QA discipline (Iron Laws, checklists, Red Flags).
+Knowledge catalogues are accessed via the `sumo_qa_load_*` tools — use them
+for principles, techniques, classifications, approaches, and specialty tool
+fits before relying on training-data knowledge.

sumo_qa-0.1.0/.github/dependabot.yml

@@ -0,0 +1,21 @@
+version: 2
+updates:
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+      time: "08:00"
+      timezone: Europe/London
+    open-pull-requests-limit: 5
+    labels: ["deps"]
+
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+      time: "08:00"
+      timezone: Europe/London
+    open-pull-requests-limit: 5
+    labels: ["deps", "ci"]

sumo_qa-0.1.0/.github/workflows/lint.yml

@@ -0,0 +1,29 @@
+name: lint
+
+on:
+  push:
+    branches: ["**"]
+  pull_request:
+    branches: [main]
+
+jobs:
+  ruff:
+    name: ruff check + format
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+
+      - name: Sync dependencies
+        run: uv sync --all-extras
+
+      - name: ruff check
+        run: uv run ruff check .
+
+      - name: ruff format --check
+        run: uv run ruff format --check .

sumo_qa-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,45 @@
+name: release
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    name: Build wheel + sdist
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+
+      - name: Build
+        run: uv build
+
+      - name: Upload artefacts
+        uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # OIDC trusted publishing
+    steps:
+      - name: Download artefacts
+        uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

sumo_qa-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,34 @@
+name: tests
+
+on:
+  push:
+    branches: ["**"]
+  pull_request:
+    branches: [main]
+
+jobs:
+  test:
+    name: pytest (${{ matrix.os }} · py${{ matrix.python-version }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        python-version: ["3.10", "3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v3
+        with:
+          enable-cache: true
+          cache-dependency-glob: "uv.lock"
+
+      - name: Set up Python
+        run: uv python install ${{ matrix.python-version }}
+
+      - name: Sync dependencies
+        run: uv sync --all-extras --python ${{ matrix.python-version }}
+
+      - name: Run pytest
+        run: uv run --python ${{ matrix.python-version }} pytest -q

sumo_qa-0.1.0/.gitignore

@@ -0,0 +1,23 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+.coverage
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.venv/
+venv/
+dist/
+build/
+.DS_Store
+.env
+
+# Per-machine MCP config written by install.py
+.vscode/mcp.json
+
+# Team-local test data fixtures. The repo ships domain-neutral samples
+# (auth/, billing/) — keep your team's actual catalogue entries local
+# rather than committing them. Add a line per domain folder you maintain
+# privately.
+knowledge/test_data/fulfilment/
+knowledge/test_data/stock/

sumo_qa-0.1.0/.opencode/INSTALL.md

@@ -0,0 +1,81 @@
+# Installing Sumo QA for OpenCode
+
+## Prerequisites
+
+- [OpenCode.ai](https://opencode.ai) installed
+- `uv` (used to install the `sumo-qa` server binary that the skills call). Get it with `curl -LsSf https://astral.sh/uv/install.sh | sh` if you don't have it.
+
+## Installation
+
+Add sumo-qa to the `plugin` array in your `opencode.json` (global or project-level):
+
+```json
+{
+  "plugin": ["sumo-qa@git+https://github.com/sumithr/sumo-qa.git"]
+}
+```
+
+Then install the MCP server binary that the skills call into:
+
+```bash
+uv tool install --from git+https://github.com/sumithr/sumo-qa.git sumo-qa
+```
+
+Restart OpenCode. The plugin registers all sumo-qa skills.
+
+Verify by asking: *"load the QA classifications"* — you should get 10 names back (api_contract_change, business_logic_change, security_change, performance_change, frontend_change, infrastructure_change, test_change, docs_change, config_change, data_migration).
+
+OpenCode uses its own plugin install. If you also use Claude Code, Cursor, Codex, JetBrains, or VS Code, install sumo-qa separately for each one.
+
+## Usage
+
+Use OpenCode's native `skill` tool:
+
+```
+use skill tool to list skills
+use skill tool to load sumo-qa/using-sumo-qa
+use skill tool to load sumo-qa/qa-deciding-approach
+```
+
+Or just describe a QA task in natural language ("plan QA for this story", "review my changes") — OpenCode's skill router picks the right one from the descriptions.
+
+## Updating
+
+```json
+{
+  "plugin": ["sumo-qa@git+https://github.com/sumithr/sumo-qa.git#v0.1.0"]
+}
+```
+
+To get the latest commit on `main`, omit the `#tag`. Some OpenCode / Bun versions cache the resolved git dependency — if updates don't appear, clear OpenCode's package cache or reinstall the plugin.
+
+## Tool name mapping
+
+If you're authoring a skill that references Claude Code tool names, OpenCode uses different names for the same tools:
+
+| Claude Code | OpenCode |
+|---|---|
+| `TodoWrite` | `todowrite` |
+| `Read` | `read` |
+| `Edit` | `edit` |
+| `Write` | `write` |
+| `Bash` | `bash` |
+| `Skill` | `skill` |
+| `Glob` | `glob` |
+| `Grep` | `grep` |
+
+The sumo-qa skills are written in tool-name-agnostic prose, so this mapping mostly matters if you fork and extend.
+
+## Troubleshooting
+
+### Plugin not loading
+1. Check logs: `opencode run --print-logs "hello" 2>&1 | grep -i sumo-qa`
+2. Verify the plugin line in your `opencode.json`
+3. Make sure you're running a recent version of OpenCode
+
+### MCP tools not available
+Confirm `sumo-qa` is on `PATH`:
+```bash
+which sumo-qa
+```
+If not, re-run the `uv tool install` step above.

sumo_qa-0.1.0/AGENTS.md

@@ -0,0 +1,97 @@
+# AGENTS.md — sumo-qa setup
+
+If you're an AI agent setting up sumo-qa for the user, follow this exactly. One command for the common case; per-host flags if you only need to wire one host.
+
+## Default: configure every detected host
+
+```bash
+python3 install.py
+```
+
+What this does:
+
+1. Installs `sumo-qa` via `uv` (prints `uv` install instructions if missing).
+2. **Claude Code** (if `~/.claude/` exists): symlinks each `skills/<name>/` into `~/.claude/skills/<name>/`. Writes `claude_desktop_config.json` with the MCP entry pointing at the absolute binary path.
+3. **VS Code + Copilot** (if cwd is a workspace with `.git` / `.vscode` / `package.json` / etc.): writes `.vscode/mcp.json` with the **VS Code-native schema** (`servers` key, `type: stdio`).
+4. **JetBrains IDEs** (if JetBrains config dir exists): prints exact Settings UI steps. JetBrains' MCP plugin requires Settings UI registration — external XML writes don't reliably register the runtime coroutine.
+5. Verifies the binary responds to JSON-RPC `initialize`.
+
+## Per-host flags
+
+Use these when you only want to configure one host:
+
+```bash
+python3 install.py --claude-code              # Claude Code only
+python3 install.py --vscode                   # VS Code workspace (cwd-based)
+python3 install.py --vscode --workspace /path/to/repo
+python3 install.py --jetbrains                # Prints JetBrains UI steps only
+python3 install.py --vscode --skip-mcp-install   # Skip uv reinstall for speed
+```
+
+Re-runs are idempotent.
+
+## VS Code specifics
+
+- VS Code reads `.vscode/mcp.json` from the **workspace root**, not from `$HOME`. install.py refuses to write to `~/.vscode/mcp.json` and prints a clear error if you're cd'd into `$HOME`.
+- VS Code uses a different MCP schema than Claude Desktop:
+  ```json
+  { "servers": { "sumo-qa": { "type": "stdio", "command": "...", "args": [] } } }
+  ```
+  install.py writes this format. Earlier versions wrote `mcpServers` (the Claude Desktop schema) which VS Code silently ignored. If you upgrade install.py and re-run, it strips the stale `mcpServers` key.
+- After running install.py, in VS Code: **Cmd+Shift+P → Developer: Reload Window**. VS Code caches the MCP server list at startup; it doesn't re-read the file mid-session.
+- Use **Agent mode** (not Ask, not Edit) in Copilot Chat. Tools require Agent mode.
+- Use a capable model — **Claude Sonnet 4.5** or **GPT-5 (full)**. Mini/fast variants don't reliably call MCP tools.
+
+## JetBrains specifics
+
+JetBrains AI Assistant's MCP config (`llm.mcpServers.xml`) is not reliably writable externally on IDEA 2026.1 — the plugin requires its in-process Settings UI to register the runtime coroutine. install.py prints the exact UI fields (with the absolute binary path):
+
+```
+Settings → Tools → AI Assistant → Model Context Protocol → + Add server
+  Name:    sumo-qa
+  Command: <absolute path printed by install.py>
+  Args:    (empty)
+  Working directory: (empty)
+Apply.
+```
+
+For **Junie** (JetBrains' agentic coding agent), drop this into `~/.junie/mcp/sumo-qa.json`:
+
+```json
+{
+  "mcpServers": {
+    "sumo-qa": {
+      "command": "<absolute path printed by install.py>"
+    }
+  }
+}
+```
+
+Or per-project at `<repo>/.junie/mcp/sumo-qa.json`. Junie reads MCP configs from those directories on startup.
+
+## Verify
+
+In any host, ask in chat:
+
+```
+load the QA classifications
+```
+
+You should get 10 canonical names back: api_contract_change, business_logic_change, security_change, performance_change, frontend_change, infrastructure_change, test_change, docs_change, config_change, data_migration. If yes, the MCP is wired correctly.
+
+## After install
+
+The host needs to re-read its MCP config:
+
+- Claude Code: restart the app
+- JetBrains IDEs: restart the IDE (or restart the AI Assistant tool window)
+- VS Code: **Developer: Reload Window**
+
+## What an AI agent can vs. must ask the user for
+
+| You (the agent) CAN | You MUST ASK the user |
+|---|---|
+| Run `python3 install.py` (with whatever host flags) | Restart their host application(s) after install |
+| Run the verification call | Anything that requires admin / sudo elevation |
+| Re-run install.py to refresh | The JetBrains AI Assistant Settings UI add (it's a clicks-only flow; can't be scripted) |
+| Verify Junie's `~/.junie/mcp/sumo-qa.json` file content | |

sumo_qa-0.1.0/DEMO.md

@@ -0,0 +1,105 @@
+# 5-minute sumo-qa demo
+
+Open any real repo. Run one of the prompts below. Watch the senior-QA workflow happen on actual code, in front of you. No staged data, no scripted output — sumo-qa walks your repo and produces senior-grade QA on whatever it finds.
+
+## Step 1 — Install (60 seconds)
+
+**Claude Code:**
+
+```text
+/plugin marketplace add sumithr/sumo-qa
+/plugin install sumo-qa@sumo-qa-dev
+```
+
+```bash
+uv tool install --from git+https://github.com/sumithr/sumo-qa.git sumo-qa
+```
+
+Restart Claude Code. That's it. The SessionStart hook auto-loads `using-sumo-qa` on every conversation; the 13 skills are slash-invocable; the 21 MCP tools are available by natural language.
+
+For Cursor / Codex / OpenCode / JetBrains / VS Code + Copilot: see [`docs/INSTALL.md`](docs/INSTALL.md).
+
+## Step 2 — Run one of these prompts on your repo
+
+Open your repo in Claude Code. Pick the prompt that matches the QA situation you actually have. Each is a one-liner.
+
+---
+
+### 1. Pre-merge safety check — *the strongest opener*
+
+```
+Review my changes — is this safe to merge?
+```
+
+**What happens:** sumo-qa reads your `git diff` directly (no asking you what changed), classifies the change shape, names 3–7 risks anchored to file + line, asks ONE focused question if anything's ambiguous, **runs your full test suite right now** (refuses to call safe-to-merge from "CI was green earlier"), maps each named risk to a covering test, and delivers SAFE / NOT SAFE / NEEDS WORK with concrete evidence.
+
+**The wow moment:** when it refuses to declare safe-to-merge because one of the risks it named has no covering test, and tells you the exact regression test to add — by file + function + assertion shape. Walk through [worked example 02](tests/scenarios/worked-examples/02-review-my-changes.md) to see the pattern.
+
+---
+
+### 2. Pre-coding QA plan — *for a fresh story*
+
+```
+Plan QA for this story before I start coding: <paste the ticket / one-liner>.
+Files likely touch <main_module.py> and <related_module.py>.
+```
+
+**What happens:** sumo-qa reads the actual files, names 3–7 risks specific to *this* change (not "edge cases"), picks one design technique per risk from the loaded ISTQB-grounded catalogue, proposes the **smallest useful test set** tied to those risks, asks you to confirm any open assumptions. No code yet — this is the prep.
+
+**The wow moment:** risks like *"currency conversion at the GBP→USD boundary rounds incorrectly when the rate is supplied with >6 decimal places"* — not *"input validation breaks"*.
+
+---
+
+### 3. Bug fix the right way — *regression-first TDD*
+
+```
+Fix this bug regression-first: <describe the bug + the likely file>.
+```
+
+**What happens:** sumo-qa walks the repo to find the production file and the sibling tests (it reads your test conventions; it doesn't ask "what framework do you use?"), picks the smallest failing test idea, confirms the one ambiguous detail with a single question, writes the failing test, runs it, **surfaces the red output verbatim** as proof, then hands off for you to make it green.
+
+**The wow moment:** it refuses to write the test AND the production fix in the same turn. The red phase is non-negotiable — the proof that the test actually catches the bug must come before the fix. Most AI assistants skip this.
+
+---
+
+### 4. Repo-wide audit + QA strategy
+
+```
+Audit our test coverage and design a QA strategy.
+```
+
+**What happens:** sumo-qa walks your repo with its file tools (services, modules, test directories, CI config), produces a per-area provisional analysis with risks anchored to file paths, walks you through 6 confirmation gates one at a time (scope → risks → specialty tool fit → prioritisation → target pyramid → phased rollout → residual risks), then offers to write the result to `docs/qa-strategy.md`.
+
+**The wow moment:** when it tells you a service that "feels well-tested" actually has 12 unit tests and zero mutation coverage on its highest-branching function — and proposes a 3-phase rollout to close the gap, with named gates at the end of each phase (not a calendar).
+
+---
+
+### 5. Multi-task QA rollout with agents — *the showpiece*
+
+```
+Plan QA for the <feature> across <module1>, <module2>, <module3> — then dispatch
+subagents to execute it in parallel.
+```
+
+**What happens:** sumo-qa runs the full agent-execution chain:
+
+1. **`qa-planning-qa-rollout`** — turns the work into a written plan at `docs/qa/plans/YYYY-MM-DD-<feature>.md` with 6–12 bite-sized tasks, each tagged with its approach and the named risk it covers.
+2. **`qa-executing-qa-rollout`** — dispatches **one fresh subagent per task** in parallel waves; each output goes through **two-stage review** (spec-correctness then test-quality) before the task is marked done.
+3. **`qa-finishing-qa-work`** — runs the full suite one last time, builds the risk-to-test coverage map, surfaces any uncovered risks honestly, writes a PR-ready summary to `docs/qa/runs/...`.
+
+**The wow moment:** watching parallel subagents write tests against different risks at once, each getting reviewed twice (once for *"did it catch the right risk?"*, once for *"is the test well-shaped?"*) before counting as done. That's how senior QA scales — and it's the gap most AI assistants don't even attempt.
+
+---
+
+## What to tell teammates after the demo
+
+> *"Install with one line. Pick a real change. Ask for a review or a plan. The AI will walk your actual repo, name risks anchored to file:line, run tests right now (not from CI memory), and either declare safe-to-merge with evidence — or tell you exactly what's missing. For multi-task QA work it dispatches subagents in parallel with two-stage review."*
+
+That's the value prop in one paragraph. Run any of the 5 prompts above on your real repo to see it.
+
+## Want to go deeper?
+
+- **All 10 scenarios documented:** [`tests/scenarios/SCENARIOS.md`](tests/scenarios/SCENARIOS.md) — every QA situation sumo-qa handles, with expected interaction shape + anti-patterns.
+- **Polished worked examples:** [`tests/scenarios/worked-examples/`](tests/scenarios/worked-examples/) — full multi-turn transcripts showing what each scenario looks like end-to-end.
+- **The 13 skills:** [`skills/`](skills/) — each one Iron-Law-enforced, with HARD GATEs and one-section-per-turn confirmation discipline.
+- **Architecture:** [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) — how the layers fit together.

sumo_qa-0.1.0/Dockerfile

@@ -0,0 +1,17 @@
+FROM python:3.12-slim
+
+ENV PYTHONDONTWRITEBYTECODE=1
+ENV PYTHONUNBUFFERED=1
+ENV QA_STANDARDS_PATH=/app/standards/packs
+
+WORKDIR /app
+
+COPY pyproject.toml README.md ./
+COPY src ./src
+COPY standards ./standards
+COPY evaluation ./evaluation
+COPY knowledge ./knowledge
+
+RUN pip install --no-cache-dir .
+
+CMD ["sumo-qa"]