Skip to content

Docs/derive test instance status from steps stage - #3606

Open
AbhishekLambda wants to merge 5 commits into
LambdaTest:stagefrom
AbhishekLambda:docs/derive-test-instance-status-from-steps-stage
Open

AbhishekLambda wants to merge 5 commits into
LambdaTest:stagefrom
AbhishekLambda:docs/derive-test-instance-status-from-steps-stage

Conversation

@AbhishekLambda

Copy link
Copy Markdown
Contributor

No description provided.

AbhishekLambda and others added 5 commits September 28, 2026 18:09
…results

Marking a step on a manual test instance now recalculates the instance
status from its full step set (TE-22833 / LTPM-1983, live on production).

- Add "How the Test Instance Status Is Derived" to the test run execution
  page: the precedence rules, worked examples, custom statuses, manual
  override, where derivation does not apply, and the org-level
  Manual Test Status setting that controls it.
- Note that bulk instance status updates count as hand-set, and that
  archived runs are not recalculated.
- Audit logs: derived status changes are recorded against the tester who
  changed the step, naming the driving step.
- Sync: a synced instance stops being marked as derived until its next
  step status change.
- System fields: custom Test Run Status values take part in derivation,
  and deleting one resets the instances holding it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Drop the execution-view screenshot placeholder and reference the org
setting screenshot at assets/images/test-run/manual-test-status-setting.png.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Also name the toggle on the settings panel so it can be found.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
In Progress is not a selectable step or test instance status today, so
listing it among the unexecuted states only confuses the rule.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Any failed step marks the instance Failed; which step it is does not
change the outcome, so the step-position detail only belongs where it is
actually visible, in the audit log entry.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant