@automatify-au/cli 0.1.9 → 0.1.11

package/README.md

@@ -120,6 +120,12 @@ All TestOps commands are invoked as `automatify testops <command>`:
 - `doctor`
   - `automatify testops doctor check`
   - `automatify testops doctor check --json`
+- `allure`
+  - `automatify allure doctor`
+  - `automatify allure doctor --json`
+  - `automatify allure doctor --issue-key ABC-123`
+  - `automatify allure open ./allure-report.zip`
+  - `automatify allure open ./allure-report.zip --no-open --port 8080`
 
 ### Advanced browse commands
 
@@ -142,6 +148,8 @@ All TestOps commands are invoked as `automatify testops <command>`:
 - `allure`
   - `automatify testops allure upload ABC-123 ./allure-report.zip --dry-run`
   - `automatify testops allure upload ABC-123 ./allure-report.zip`
+  - `automatify testops allure download ABC-123 --output-dir ./downloads`
+  - `automatify testops allure open ./allure-report.zip`
 - `auto`
   - `automatify testops auto --dry-run`
   - `automatify testops auto`
@@ -150,6 +158,7 @@ All TestOps commands are invoked as `automatify testops <command>`:
 
 Purpose:
 - upload an already generated Allure HTML report ZIP to a Jira issue as evidence.
+- download an uploaded Allure HTML report ZIP from a Jira issue for local inspection.
 - parse `widgets/summary.json` from the ZIP and add a concise Jira comment with result counts.
 - keep the flow Java-free and backend-free; this command does not generate Allure reports from raw `allure-results`.
 
@@ -216,6 +225,59 @@ After a real upload, JSON output includes Jira attachment metadata when Jira ret
 }
 ```
 
+Download the latest Allure report ZIP attachment from a Jira issue:
+```bash
+automatify testops allure download ABC-123 --output-dir ./downloads
+```
+
+Download selection rules:
+- `--attachment-id <id>` downloads one exact Jira attachment.
+- `--filename <name>` downloads the newest attachment with that filename.
+- without either flag, the CLI chooses the newest `allure-report*.zip` attachment, then falls back to the newest `.zip` attachment.
+- existing local files are not overwritten unless `--force` is passed.
+
+Download dry run / JSON:
+```bash
+automatify testops allure download ABC-123 --dry-run --json
+```
+
+Allure preflight:
+```bash
+automatify allure doctor
+```
+
+`automatify allure doctor` checks:
+- Jira site/email/API token resolution for direct Allure upload/download.
+- optional Jira issue access only when `--issue-key` is passed.
+- `unzip` availability for manual local ZIP inspection.
+- Java availability as a warning-only optional check for future raw `allure-results` workflows.
+- Allure CLI availability as a warning-only optional check.
+
+Generated Allure HTML ZIP upload/download/open does not require Java or the Allure CLI.
+
+Optional live Jira issue check:
+```bash
+automatify allure doctor --issue-key ABC-123
+```
+
+### Open a generated Allure HTML report locally
+
+```bash
+automatify allure open ./allure-report.zip
+```
+
+`automatify allure open <zipPath>` and `automatify testops allure open <zipPath>` extract the report into a temporary directory, start a Java-free Node static HTTP server on an ephemeral port, and open the URL in your default browser. This is useful after downloading an Allure ZIP from Jira.
+
+Options:
+- `--port <n>` fixed port (default `0` for an OS-assigned free port).
+- `--host <h>` bind host (default `127.0.0.1`).
+- `--extract-to <dir>` extract into a chosen directory; the directory is preserved on shutdown.
+- `--keep` preserves the auto-created temp extract directory on shutdown.
+- `--no-open` skips browser launch for CI/headless checks.
+- `--json`, `--dry-run`, `--verbose`.
+
+The server stays alive until Ctrl+C / `SIGTERM`. URL path traversal and malformed paths are rejected.
+
 ### Optional gated maintenance commands
 
 - `sync`
@@ -369,6 +431,7 @@ automatify testops bdd features export --project-key DEV --output-dir ./artifact
 automatify testops runs show --project-key DEV --id <RUN_ID> --json
 automatify testops config validate
 automatify testops doctor check --json
+automatify allure doctor --json
 ```
 
 Advanced browse examples: