🚀 Quick Start
- Knowledge Base — Click "Knowledge Base" in the header. The AI automatically syncs reference manuals from Google Drive. These teach the AI your writing style, formatting and tone.
- Project Name — Enter the campaign or project name (appears in the document header and footer).
- Output Language — Select the language for the generated output. Use "Auto-detect" to match the language of uploaded sources.
- AI Model — Choose the model best suited to your task:
- GPT-5.6 Luna Pro — Cost-efficient OpenAI default.
- GPT-5.6 Terra Pro — Higher-quality reasoning for complex deliverables.
- GPT-5.6 Sol — OpenAI flagship for the most demanding work.
- Claude Sonnet 5 — Anthropic's current balanced model.
- Qwen 3.7 Plus — Efficient long-context generation.
- GLM 5.2 — Z.ai's current reasoning model.
- DeepSeek V4 Pro — High-quality output with DeepSeek's latest model.
- Choose output type:
- Bug Hunting Manual — Creates a Google Doc with narrative use cases (max 6), written for the Tryber community. Professional, precise, styled per UNGUESS parameters.
- Testbook — Creates a Google Sheet with all test suites, cases and steps. Full test coverage across every scenario from your sources.
- Unmoderated Usability Test Manual — Creates a Google Doc with a complete unmoderated usability test script: objective, method, use cases with thinking aloud protocol, pre/post surveys.
- Upload sources — Functional analysis PDFs, requirements, DOCX specs, screenshots, screen recordings.
- Click "Generate" and wait for the AI to produce the deliverable.
🔄 Updating Existing Manuals
Enable the "Update existing manual" toggle (visible under Output Type when Bug Hunting Manual or UT Manual is selected). Upload the existing document as a source file — the AI will use it as the base and apply only the requested changes, highlighting all additions and edits with yellow markers. Without the toggle, uploaded documents are treated as reference material only and a new manual is generated from scratch.
Client comments in DOCX: if the uploaded DOCX contains reviewer comments, the tool reads them (author, date and the commented passage) and applies them as change requests. Fill in the optional Client name(s) field to mark only those authors' comments as binding client requests — comments from other authors are treated as internal notes. Leave it empty to apply all comments.
Update the original Google Doc in place: paste the Doc URL in the Original Google Doc URL field instead of uploading a file. The tool reads the Doc and its unresolved comments straight from Drive, automatically restores the documentation used when the manual was first generated (so context isn't lost between sessions), and shows a preview with highlighted changes. Nothing is written until you click Approve — then a backup copy is created on Drive, each client comment gets a reply ("Modifica applicata…") and is marked as resolved (the client receives the notification and finds the closed threads in the Doc's comment history), and the original Doc is updated in place: same link, same sharing with the client. Comments from other authors stay open when client names are specified. Works only for Docs created by this tool.
👥 Tester Groups (Tryber)
Describe tester groups in General Context (e.g. "Groups: 1, 2, 3..."). The AI will:
- Add a TESTER GROUPS section at the top of the manual
- Create sub-use-cases (UC 1a / UC 1b) when a flow diverges between groups
- Each group's UC is self-contained — the Test Leader will assign/hide the correct one on Tryber
🎨 Figma Integration
Add Figma links in the dedicated field. The AI will reference them in the generated output so testers can consult the design. For protected Figma files, upload screenshots instead.
📂 Supported Inputs
| Type | Formats | Description |
|---|
| 📄 Documents | PDF, DOCX | Functional analysis, requirements, existing test manuals |
| 📊 Spreadsheets | XLSX, XLS | Requirements matrices, data tables |
| 🖼️ Images | PNG, JPG, WebP | UI screenshots, mockups — analyzed by AI vision |
| 🎬 Videos | MP4, WebM, MOV | Screen recordings — frames extracted and analyzed by AI |
| 🌐 URLs | Web links | Product pages — auto-scraped |
| 🎨 Figma | Figma links | Design references — linked in the output |
⚙️ General Context Tips
Use the General Context field to fine-tune generation:
Tester groups: 50% Prospect, 50% Existing — enables group clusteringInclude accessibility tests — adds WCAG accessibility testingGenerate more than 6 use cases — removes the 6 UC limitFocus on payment flows only — narrows test scopeOut of scope: admin panel, settings — excludes areasModify the uploaded manual adding X — triggers manual modification mode
📋 Output Details
Bug Hunting Manual (Google Doc) — Max 6 narrative use cases for the Tryber community. Styled with UNGUESS branding. Supports tester group clustering (UC 1a/1b) when groups are defined. Created on your personal Drive — move to the campaign folder when ready.
Testbook (Google Sheet) — Complete test coverage across all suites, cases and steps. Sheets: Istruzioni (compilation guide), Sommario (project info + TC import cell), Recap Totale (per-tester status counters), plus one Tester N sheet per tester with device info block, colored status counters, per-step Esito dropdown (TO DO/OK/OK con Defect/KO/Skipped) and Bug ID column. Includes Figma references when provided.
Unmoderated Usability Test Manual (Google Doc) — Complete unmoderated usability test script. Sections: NOTE, OBIETTIVO, METODO, SET UP (USE CASE 0), SURVEY INIZIALE, USE CASE 1..N (tasks + thinking aloud + post-task questions), SURVEY DI USCITA. Supports summative studies (CES/CSAT metrics) when specified in context.
