Sinra integrates QA test cases directly into the development cycle. Create test cases on capabilities, run them during the cycle, and track acceptance without leaving the platform.

What are Testings?

Testings are QA test cases attached to capabilities. Instead of maintaining a separate tool like TestRail, your QA team creates and runs test cases directly in Sinra, linked to the feature they validate.

Creating a Test Case

Any user with Reporter access or above can create a testing on a capability:

Open the capability
Click “Add Testing”
Set the test name, description, and expected result
Assign to a QA user
Optionally, choose the issue it Verifies

The breadcrumb of a testing shows its capability: Home, capability, testing.

Verifying a Specification or a Bug

A testing can say which issue it verifies. The field only offers a specification or a bug of the testing’s capability, plus the bugs without a capability that Concern it. Plans and tasks cannot be tested, and templates never are. The link is optional: a testing can still cover the whole capability.

The testing page shows the verified issue, clickable.
The page of a specification or a bug lists the testings that verify it, with their state, and offers Add a test with the capability and the issue already filled in.
On the capability page, each specification shows its number of tests, or No test yet.
Rejected or not, a testing that points at a specification counts it as tested.

An issue verified by at least one testing cannot be deleted, moved to another capability, or changed through the API to a type that cannot be tested, until the testings are deleted or detached. The message gives the number of tests.

Running Tests During a Cycle

The /testings/current view shows all test cases in progress for the active release. QA runs each test and marks it:

Result	Meaning
Accepted	Test passed, feature validates
Rejected	Test failed, linked issue should be reopened or a bug created

Rejected tests surface immediately in the capability view, giving developers and product owners real-time QA status.

Traceability

Testings connect capability to validation:

Capability → Specification → Testing → Accepted / Rejected

When a release is delivered, you can review which capabilities had all tests accepted vs which had rejections that were overridden or deferred. This audit trail is preserved in the release retrospective.

Coverage Gaps

The coverage gaps widget of the tester dashboard lists the active specifications that have no testing at all, with their capability and release, next to the two existing indicators. Only testings count: a specification marked done is still a gap if nothing verifies it. Existing testings keep no link until you set it, so existing specifications appear as untested at first.

See Traceability for the full chain.

Why Integrated QA Matters

Switching between a ticket tool and a separate QA tool creates synchronization problems: bugs found in TestRail need to be manually created in Jira. Sinra eliminates this handoff. A rejected test case is linked directly to the capability and cycle where the fix belongs.

Testings (QA)