feat(scenario): tag run log entries with their context

- scenario_run_logs gains a context column (step:N, snippet:alias,
  assertion:pass/fail, run), tracked through a call stack in
  CodeExecutorService so nested runSnippet calls tag their own and
  inner log lines
- automatic step started/passed/failed entries and the Playwright
  trace upload notice are tagged accordingly
- run log export (CSV/Markdown) and the logs search match context
  as well as message
- add a LogOutput UI component: a terminal-style log viewer with
  level color coding, elapsed-time-since-start timestamps and a
  context tag, replacing the generic Table on the run detail page
- show the full log list instead of paginating it, capped to a
  scrollable block
- fix migrations.spec.ts's revert test, which only undid the last
  migration instead of all of them
This commit is contained in:
ars9 committed 2026-10-01 13:26:07 +03:00
1 parent 5152fffe82
commit 6cba785e2f
15 files changed
+383 -70

No files matched your search

+4 -2
View File
@@ -48,12 +48,14 @@ describe("Database migrations", () => {
}
});
it("can revert the initial migration", async () => {
it("can revert all migrations", async () => {
const dataSource = new DataSource(dataSourceOptions(":memory:"));
await dataSource.initialize();
try {
await dataSource.runMigrations();
await dataSource.undoLastMigration();
for (let i = 0; i < MIGRATIONS.length; i++) {
await dataSource.undoLastMigration();
}
const tables = await dataSource.query(
`SELECT name FROM sqlite_master WHERE type = 'table' AND name NOT IN ('migrations', 'sqlite_sequence')`,
);