Skip to main content

QA Session

Use this workflow when QA needs stable, repeatable runtime behavior for bug validation.

Session design​

  • freeze one known config revision
  • avoid mid-session config edits
  • keep test data setup explicit (oneshot services or scripts)

Example launch:

flowlayer-server -c ./flowlayer.qa.jsonc -s 127.0.0.1:6999 -token qa-token

During the session​

  1. QA validates service states in TUI.
  2. QA reproduces the scenario.
  3. Team captures relevant logs with get_logs and after_seq.
  4. Team restarts only impacted services (restart_service) to keep context stable.

Why this helps​

  • one shared runtime view avoids conflicting local assumptions
  • sequence numbers make log continuity explicit
  • selective restart reduces rework during investigation

For log continuity details, see Logs and Snapshot vs Live Events.