Skip to main content

​
Manual Tests & Gherkin

​
Choose your format upfront

On the Manual tests tab, pick the format before generating:
  • Classic steps — Action / Expected Result rows.
  • Gherkin BDD — a Given / When / Then scenario.
TestForge then generates a single, editable representation in the format you chose. There is no second copy and no post-generation view toggle, and there is no separate format choice at push time — the format is decided once, upfront.

​
Edit before push

Whatever the format, every case is editable in place:
  • Edit the title inline.
  • Change the priority via the P1–P4 dropdown.
  • Edit the content — Action / Expected steps in Classic mode, or the Given/When/Then scenario (in an editable field) in Gherkin mode.
  • Delete a test case with the ✕ at the top right of the card.
The push always uses what you edited, never a frozen generated view.

​
Pushing to ADO

Tests are pushed via the Tested By relation and appear in the Test Coverage tab of the work item. In Gherkin mode, the ADO steps are derived from your edited scenario — keyword recognition is bilingual (English or French):
  • Given / When / And (before Then) — or Soit / Étant donné / Quand / Lorsque / Et (before Alors) → Action step.
  • Then / And / But (after Then) — or Alors / Et / Mais (after Alors) → Validation step (Verify:, or Vérifier : for French stories, in the action field; the line text as the expected result).
The full scenario is also written to System.Description.
In Gherkin mode the push needs at least one recognisable step — Given / When / Then or their French equivalents (Soit / Étant donné / Quand / Lorsque / Alors). If the edited scenario has none in either language, the push is blocked with an actionable message — there is no silent fallback to classic steps. Fix the scenario, then push.
You do not need an Azure DevOps Test Plans licence to push manual tests. A Basic licence is sufficient.