TAMASH · Forge

From a developed feature
to a signed-off release.

Test cases, cycles, executions, reports and a live dashboard, connected to the repository. The GenEx Agent explores the application and drafts tests while the team plans and signs off releases. Shield and RunSights are included.

For QA teams, developers and the agents that work with them.

Forge · Quality overviewRelease stage
Active cycles2CY-12 running, CY-13 planned
Failed and blocked32 failed · 1 blocked
Not run yet4of 44 in active cycles
Release health · CY-12 Checkout, October release38 of 44 passed · 2 failed · 1 blocked · 3 not run · sign-off waiting on 2 fixes
  • FailedTC-164Coupon applied twice on a retried payment
  • BlockedTC-171Staging has no sandbox for the card provider
The idea

Two stages of quality.
Never mixed.

What is built while the feature is made, and what is proven when the release is tested. Forge keeps them apart, and a person promotes from one to the other.

Development stage

Built while the feature is made

Scenarios, automated specs, pages and locators, findings and proposals from the GenEx Agent, developers and QA. Informal, continuous, never counted as release results.

  • Explore: what the agent found in the application
  • Proposals waiting for a person's decision
  • Development quality dashboard
Release stage

Proven when the release is tested

Cycles run against accepted test versions, with evidence on every attempt and sign-off at the end. The formal record a release is judged on.

  • Published test cases, versioned
  • Cycles, executions, defects and evidence
  • Release health, readiness and sign-off
Five modules

Everything a release needs,
in the order a team meets it.

01

Test cases

A versioned library in folders: steps tables or Gherkin, custom fields, import and export. Authors publish directly or another author approves.

02

Test cycles

Chosen tests in an environment over a period: plan, assign, run, then readiness and sign-off.

03

Executions

A step-by-step runner on desktop or phone. Every attempt keeps its evidence and defects, and CI results join the same history.

04

Reports

Ready-made reports, a builder, traceability to requirements, exports and fixed snapshots.

05

Dashboard

Where the project stands and what needs attention, arranged by each person.

The GenEx Agent inside Forge

It explores, drafts and validates.
People decide.

  • Explore. The agent maps screens, fields, controls and server calls, and reports findings as broken, should fix, or a note.
  • Propose. From a finding or a scenario it drafts a test case. An author accepts, edits or declines it.
  • Generate. Reusable Playwright or Cucumber automation, with pages and locators the team can see.
  • Validate. It runs scenarios against the developed feature. Its runs stay in the development stage until a person promotes them.

The agent never presses Save, Delete or Submit.

Explore · FindingsAgent connected
Screens known31
Open findings7
Proposals to review5
  • BrokenCheckout · PaymentPay now returns 500 when the coupon field is empty
  • Should fixAccount · AddressesSave keeps focus on the postcode after an error
  • NoteOrders · HistoryTwo rows share the label "Order 10342"
AI that suggests. People who decide.

Less writing. Less planning.
The same judgement.

Every suggestion is something to accept, edit or decline. None changes a result.

Generate tests from requirements

From Jira stories or pasted text, a draft test case per acceptance criterion, linked to its source.

Explain failures

A likely cause for a failed attempt, the application, the test or the environment, with similar failures grouped. Advice only.

Find coverage gaps

The stories with no tests, and an offer to write them.

Create a cycle with AI

A proposed scope from the release, the environment and the time you have, with a reason beside every test.

Also: convert scenarios into test cases, suggest steps from a title, improve an existing case, and draft report summaries. Use TAMASH's AI or your organization's own key.

Connected to your tools

Quality information stays in one place.

Jira

Requirements and defects: tests from stories, defects from failed attempts, coverage traced back.

Repository and CI

Automated tests linked to their cases, and CI results arriving as executions, with how much of the suite is automated.

People and roles

Project admins, authors, executors and viewers, with Org Admins over every project. Single sign-on and custom roles for enterprises.

Bring a release. Leave with the evidence.

Let the agent explore your application while your team plans the first cycle.