Your workspace.
Every workflow, explained.

Getting Started

1.1 What ElixirIQ Is, in One Paragraph

ElixirIQ is a test management platform that replaces the usual mess of spreadsheets, disconnected bug trackers, and manual test writing with one connected workspace. It combines structured manual testing (projects, cycles, test cases) with AI features (requirement analysis, autonomous testing agents) and native Jira integration, so your whole QA lifecycle — planning, execution, defects, and reporting — lives in one place.

1.2 Creating Your Company Workspace

• Sign up and create your Company Workspace — this is the top-level container for your organization's projects, users, and settings.
• You can create your account the traditional way (email + password) or use Google Social Auth for one-click sign-in.
• Once your workspace exists, invite your teammates so they can start collaborating on projects, test cases, and defects right away.

1.3 Logging In

• Email login: standard email and password sign-in.
• Google Social Auth: sign in instantly with an existing Google account — useful for fast enterprise onboarding without managing another password.

1.4 Quick Start: 3 Steps to Your First Project

Create your workspace (or log in via Google) and invite your team members.

Upload your existing Excel roadmap to instantly generate modules and requirements.

Execute test cycles, sync defects with Jira, and export Traceability Reports for release sign-off.

Dashboard & Workspace Overview

2.1 Navigating the Workspace

Once inside ElixirIQ, your work is organized in a clear hierarchy:

Project → Sprint → Module → Requirement → Test Scenario → Test Case Understanding this hierarchy is the key to understanding everything else in ElixirIQ, every feature (traceability, reporting, defects) is built around these six levels.

2.2 What Lives at Each Level

Project Setup & Roadmap Import

3.1 The Roadmap Method: Instant Project Creation

Instead of manually typing out every module and requirement (which is how legacy tools like TestRail or Zephyr force you to start), ElixirIQ lets you upload an existing product roadmap in Excel (.xlsx) format.

How it works:

1. Prepare or export your product roadmap as an .xlsx file.
2. Upload it into ElixirIQ.
3. ElixirIQ automatically parses the file and generates modules, user stories, requirements, and foundational test scenarios for you.

Why it matters: This is a 1-click setup that eliminates days of manual data entry — what used to take a QA lead a week of copy-pasting into spreadsheets now takes minutes.

3.2 Structured Hierarchy Setup

After import, confirm or adjust the generated structure (Project > Sprint > Module > Requirement) before moving into test planning. This structure is what powers the Traceability Matrix later, so it's worth reviewing carefully at this stage.

Test Planning, Cycles & Execution

4.1 Creating Test Scenarios & Test Cases

• Build test scenarios under each requirement, then break them down into individual test cases with clear steps.
• Test cases can be grouped formally under a module/requirement, or kept as Ungrouped Test Cases for exploratory or standalone testing that hasn't been assigned to a formal cycle yet.

4.2 Flexible Test Cycles

A Test Cycle is a curated, targeted run of test cases. ElixirIQ supports multiple cycle types so you can scope testing to the situation:

• Smoke — quick check that the build isn't fundamentally broken.

• Sanity — rapid validation checks for continuous deployment pipelines (see Sanity Checklists below).
• Regression — broader re-testing to catch anything a new change may have broken.
• Release-specific — a custom cycle scoped to what's shipping in a particular release.

4.3 Sanity Checklists

Lightweight, rapid build-validation checklists designed to run quickly against every new build, ideal for teams shipping continuously and needing a fast "is this build even testable" gate.

4.4 Executing Tests & Recording Results

While executing a test case, testers can mark each step as:

• Passed
• Failed
• Blocked
• Skipped Each result can carry screenshots and execution timing, giving you a rich, auditable execution history, not just a pass/fail number, but the evidence behind it.

Traceability Matrix

5.1 What the Traceability Matrix Does

The Traceability Matrix is ElixirIQ's answer to the "fragmented spreadsheets, broken links" problem in legacy tools. It gives you 360-degree visibility — from a business requirement all the way down to the production bug ticket it eventually generated.

5.2 Multi-Dimension Grouping

Switch how you view the matrix depending on what question you're trying to answer:

• Sprint-based view — what's covered in this iteration?
• Module-based view — how well-tested is this feature area?
• Requirement-based view — is this specific business need fully covered?

5.3 Recursive Status Aggregation

Parent nodes (e.g., a Module) automatically roll up status and coverage percentages from all of their child entities (Requirements → Scenarios → Cases) beneath them. You don't have to manually calculate coverage — ElixirIQ aggregates it for you as testing progresses.

5.4 Exporting Traceability Reports

With one click, export an audit-ready traceability report in whichever format your stakeholders need:

• Excel (.xlsx)
• PDF
• Microsoft Word (.docx)
• CSV

AI-Powered & Agentic Testing

6.1 Autonomous Agentic Testing

ElixirIQ can deploy autonomous browser agents (powered by Playwright MCP) that explore your target web application on their own — executing multi-step user journeys and reporting regressions without anyone writing a manual test script. This is a step beyond "AI-assisted" testing: the agent actively navigates and tests, rather than just suggesting test text.

6.2 Automated Web Scans

Zero-code URL scans that check:

• Accessibility (WCAG compliance)
• Responsive design breakpoints
• DOM assertions Just provide a URL — no scripting required — and ElixirIQ runs the scan and reports the results.

AI Requirement Analysis & Gap Coverage

7.1 How Requirement Analysis Works

Feed ElixirIQ your raw user stories or specifications, and its LLM-based analysis engine audits them to automatically surface untested edge cases you might otherwise miss.

7.2 Real-Time Coverage Scoring

As you build out test scenarios and cases, ElixirIQ shows an instant percentage score indicating how much of a requirement is actually covered by testing — so gaps are visible before release, not after.

7.3 Executive Gap Analysis PDFs

Generate high-resolution PDF reports summarizing untested business risk, written for a stakeholder audience rather than a QA audience — useful for release sign-off conversations with people who don't live in the test suite day-to-day.

7.4 Competitive Analysis PDFs

Automated benchmarking reports that compare your quality metrics against industry standards, generated directly from your testing data.

Defect Management & Jira Sync

8.1 Logging a Defect

When you find a bug during execution, log it with:

• Severity: Blocker, Major, Minor, or Trivial
• Priority
• Steps to reproduce
• Screenshots

8.2 Jira Cloud Synchronization

• Connect ElixirIQ to your Atlassian Jira Cloud instance via OAuth 2.0.
• Push defects directly into Jira as native issues — no copy-pasting between tools.
• Status updates sync bi-directionally and in real time: if someone changes the issue status in Jira, ElixirIQ reflects it, and vice versa. Why it matters: Legacy tools typically only offer one-way CSV export or manual copy/paste into the bug tracker. ElixirIQ keeps both systems in sync automatically.

Analytics & Reports

9.1 Sprint Release Report

An executive summary covering passed/failed ratios, bug density, and overall test throughput for a given sprint or release.

9.2 Flaky Test Detector

Automatically identifies unstable or non-deterministic test cases — the ones that pass sometimes and fail other times with no code change — so your team can fix or quarantine them instead of losing trust in the whole suite.

9.3 Error-Prone Area Heatmap

A visual heatmap that highlights which modules have the most frequent defect recurrence, helping you direct testing effort where it's actually needed.

9.4 Test Closure Workflow

Formal sign-off workflow for wrapping up a test cycle or release, including:

• Test Incident Reports (TIR)
• Closing Notes

Client Portal

10.1 What the Client Portal Is

A dedicated, read-only access mode for people outside your core QA team, external clients, auditors, or executive stakeholders — who need visibility into testing progress without the ability to edit anything.

10.2 What External Users Can See

• Testing progress
• Passed/failed ratios
• Traceability reports They cannot edit test cases, defects, or any underlying data, this avoids accidental modifications while still giving transparency. Legacy tools typically require buying a full paid seat just to give a client this kind of visibility; ElixirIQ separates viewing from editing by design.

QA Team Performance & Recognition

11.1 Performance Sheets

Quarterly and monthly evaluation rubrics that measure things like test creation efficiency and bug discovery quality, a built-in, structured way to evaluate QA team members rather than relying on ad hoc manager notes.

11.2 Star of the Month (SOM)

A peer-nominated recognition system built directly into the platform, so team excellence gets celebrated inside the same tool the team works in every day.

Integrations

Administration, Security & Governance

13.1 Multi-Tenant Isolation

Strict data isolation ensures no tenant (company) can ever access another company's data — even though everyone runs on the same platform.

13.2 Roles & Permissions (RBAC)

A granular permissions matrix across five default roles:

• Super Admin
• Company Admin
• Project Manager
• QA Tester
• Read-Only Viewer

13.3 In-App Knowledge Base

Create company "Books," chapters, and SOPs directly inside ElixirIQ — so process documentation lives next to the work it describes, instead of in a separate wiki no one checks.

13.4 AI Budget Controls

• Set tenant-wide AI credit ceilings.
• View daily token breakdowns.
• Keep AI usage costs predictable rather than an open-ended bill at the end of the month.

13.5 Help Desk & Support

A contextual, in-app slide-over drawer with FAQs and support ticketing — help is available without leaving the platform.

13.6 Data & Security Practices

• Encryption in transit (HTTPS/TLS 1.3) and at rest.
• Multi-tenancy isolation enforces strict data separation between companies.
• Proprietary prompts sent to ElixirIQ's AI analysis models are never used to train public machine learning models.

Subscription Plans & Billing

14.1 Plan Comparison

14.2 What Happens If You Exceed Your Plan

ElixirIQ never deletes your historical test cases or project data if you downgrade or exceed tier limits. Instead:

• A Resource Freezing Engine temporarily freezes assets beyond your limit.
• A Downgrade Wizard lets administrators choose exactly which assets stay active until the plan is upgraded again.

Frequently Asked Questions

Glossary of ElixirIQ Terms