Logflare / logflare / b41b62bf008f3673a992491bfa64c54e8d39127a
80%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 473
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 79.489% (+0.02%) from 79.469%
b41b62bf008f3673a992491bfa64c54e8d39127a

push

github

web-flow 
test: stabilize and instrument Supabase E2E logs.spec.ts (#3439)

* test: add E2E diagnostic hooks

Adds beforeEach/afterEach hooks in test/e2e/supabase/features/logs.spec.ts
that, on test failure, attach the rendered table HTML, captured browser
console + pageerror events, and the current page URL as Playwright test
artifacts. Captures state from intermittent CI failures that don't
reproduce locally.

* ci: fix Playwright report artifact upload

The Supabase integration workflow uploads `playwright-report/` as an
artifact after each browser run. Two issues prevented retrieval:

1. The `path` was relative to the repo root, but `npx playwright test`
   ran in `test/e2e/supabase/` (per `defaults.run.working-directory`)
   and wrote the report there. `actions/upload-artifact@v4` is a `uses:`
   step and does not honor `defaults.run.working-directory`, so it found
   no files. CI logs showed:
   `##[warning]No files were found with the provided path: playwright-report/.`

2. All three matrix entries (chromium/firefox/webkit) uploaded under the
   same artifact name `playwright-report`. `actions/upload-artifact@v4`
   enforces unique names per workflow run; subsequent uploads fail.

Both fixed: scope the path to the working directory, and include the
matrix project in the artifact name so each browser gets its own report.

* test: capture network requests and table text in E2E diagnostics

Investigation of the prior failure capture surfaced two gaps:

1. The captured table HTML is React Data Grid markup and was hard to
   compare against `expect.toContainText(...)` assertions, which operate
   on textContent. Adds `table.txt` alongside `table.html` so the
   assertion-relevant view is one click away.

2. The diagnostic answered "did the page render the empty state?" but
   could not answer "did the API actually return zero results, or did
   the search request error / never fire?" Adds `network.json` capturing
   request/response pairs (method, URL, status... (continued)

12343 of 15528 relevant lines covered (79.49%)

4868.47 hits per line

Coverage Regressions

Lines Coverage ∆ File
1
30.77
 -3.85% lib/logflare/sources/source/text_notification_server.ex
Jobs
ID Job ID Ran Files Coverage
1 b41b62bf008f3673a992491bfa64c54e8d39127a.1 473
79.49
 GitHub Action Run
Source Files on build b41b62bf008f3673a992491bfa64c54e8d39127a