TestingOps.ai

Issue trackers, wikis and code · Native connection

Confluence and TestingOps: your specifications as test knowledge

Analysis documents, business rules and decisions usually live in Confluence. TestingOps reads the pages of a space into its knowledge base, so AI test agents write and review test cases with that material in view.

  • Native connection
  • Available
Request a demo Atlassian: manage API tokens for your Atlassian account
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Confluence and TestingOps in short

The Confluence connection reads the pages of one Confluence space per link into a TestingOps project's knowledge base as know-how documents. Agents use them as context when they write, review and fix test cases.

Pages are read with the permissions of the connecting account, up to 300 per space, and a page is read again only when its version changes. Agents can also search the space and open a page live while they work.

Connect Confluence Cloud with an account email and API token or with Connect with Atlassian; Data Center uses a personal access token. TestingOps uses Confluence as a read source.

What it does

What it does for your testing

  1. 1

    Specifications become know-how

    Input
    The pages of a space: title, body and address
    TestingOps
    Turns each page into a know-how document in the project's knowledge base; pages whose version did not change are skipped
    Output
    Context with a link back to the source page
  2. 2

    Business rules reach case writing

    Input
    A rule written on a page, such as a limit or an error message
    TestingOps
    Comes up in the knowledge search when an agent writes, reviews or fixes a case on that topic
    Output
    Cases and fixes written with the rule in view
  3. 3

    Removed pages leave the knowledge base

    Input
    A page deleted or archived in the space
    TestingOps
    Retires its document at the next sync that reads the whole space
    Output
    Agents no longer see the outdated text
  4. 4

    Current text during a task

    Input
    An agent needs a page that changed after the last sync
    TestingOps
    Searches the space with a query limited to that space and opens the page
    Output
    The page's current text, only from the linked space

Step by step

How it works

  1. Connect ConfluenceUnder Integrations → Project tools, open Confluence. For Cloud, use Connect with Atlassian or enter the wiki address, your account email and an API token; for Data Center, enter the wiki address and a personal access token.
  2. Link a spaceIn Knowledge Base, add a space under Wikis. Each sync reads up to 300 current pages of the space.
  3. Pages become know-howEach page becomes a know-how document of the project; unchanged versions are not read again, and pages that disappear are retired.
  4. Agents use itAgents find the pages through the knowledge search when they write, review or fix cases, and can search the space live for the latest text.

Syncs run hourly and on Sync now. If you paste the address of a page as the wiki address, it is cut back to the wiki root.

Connect

Setup

  1. In TestingOps, open Integrations → Project tools and select Confluence.
  2. Cloud: choose Connect with Atlassian, or enter your wiki address (https://<site>.atlassian.net/wiki) as Base URL, the account email under Email (Confluence Cloud) and an API token. Data Center: enter the wiki address and a personal access token in the API token field.
  3. If the wiki is only reachable inside your network, pick its gateway under Connect through a private network, then select Test connection and Connect.
  4. In Knowledge Base, pick the project, select + Add source under Wikis, choose the connection, select the space and select Link to RAG.

Documentation: Atlassian: manage API tokens for your Atlassian account · Atlassian: using personal access tokens (Data Center)

Where you connect it in TestingOps: Integrations → Project tools → Issue trackers, wikis and code → Confluence

Use cases

Use cases

Write cases from an analysis document

Trigger
A feature's analysis page is published in the linked space
Uses
The page text after the next sync
Agent activity
Agents find it in the knowledge search when they write the feature's cases
Result
Cases whose steps and expected results follow the rules on the page
Condition
Up to 300 pages per space link

Fix a failing case against the documented rule

Trigger
A case is fixed with AI after a failed run
Uses
Up to six knowledge-base sources nearest to the case, Confluence pages included
Agent activity
Proposes a corrected case with those sources in view and shows which sources it used
Result
A fix proposal a person accepts or rejects
Condition
A source that has not synced for a day is flagged as possibly stale

Keep a Data Center wiki inside the network

Trigger
The wiki is only reachable over the company VPN
Uses
A private network gateway chosen on the connection
Agent activity
Syncs and live searches go through the gateway
Result
Pages available as with Confluence Cloud
Condition
Data Center uses a personal access token

Capabilities

Capabilities and limits

What is read

  • Pages of one space per link: title, body as text, version and address; up to 300 current pages per sync
  • On demand for agents: search within the linked space and the current text of a page in that space

What is produced

Know-how documents in the project's knowledge base, one per page, refreshed when the page version changes

Where it can write

Nothing in Confluence. Confluence links have no switch that lets agents create or edit pages, and defects cannot be filed to Confluence.

How it connects

  • Confluence Cloud: Connect with Atlassian (read-only scopes) or account email and API token
  • Confluence Data Center: a personal access token; an email in the form is ignored
  • Optional: a private network gateway

Account and permissions

  • Pages are read with the permissions of the token owner or the signed-in Atlassian user
  • Pages the account cannot see are not read

Limits

  • 300 pages per space link, one space per link
  • Comments and attachments are not read
  • Deleted pages are retired only when the space fits in one sync of 300 pages
  • Connect with Atlassian works for Cloud sites on atlassian.net only

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A team keeps the analysis for its loan application in a Confluence space, including a page that says applicants under 18 are refused with the message "Applicant must be at least 18".

After the space is linked, an agent writing cases for the application form finds that page in the knowledge search and adds a case for a 17-year-old applicant with that exact message as the expected result.

Frequently asked questions

Can TestingOps generate test cases from Confluence requirements?

Agents write cases with the pages in view: each page becomes know-how in the project's knowledge base, and the knowledge search brings it up when an agent writes or reviews cases on that topic. There is no separate button that turns a page into cases.

Does TestingOps write to Confluence?

No. Confluence is a read source: its links have no switch that lets agents create or edit pages, and defects go to an issue tracker instead.

How current is the copy?

Syncs run hourly and on Sync now, and only pages whose version changed are read again. For the latest text during a task, agents open the page live.

Which pages are read?

The current pages of the linked space that the connecting account can see, up to 300 per sync. Comments and attachments are not read.

Does it work with Confluence Data Center?

Yes, with a personal access token. If the wiki is only reachable inside your network, the connection can use a private network gateway.

What does Connect with Atlassian allow?

Reading only: it asks Atlassian for read access to content, spaces and search on your Cloud site.

Next step

Bring a Confluence space with a real specification to a demo and see which cases agents write from it.

Request a demoMore project tools integrations