Epic #705. No e2e/playwright/*blog* spec exists; coverage is only the generic route walk (/blog public, /blog/create auth). The owner-delete flow (angular #420) shipped with data-testid="blog-entry-delete-button" and the shared confirm dialog's testids, so the selectors are ready.
Shape:authenticated-blog-delete.spec.ts (fixtures import per e2e conventions): create a post as the e2e user → verify it renders on /blog → delete via the testid + confirm-dialog-confirm → verify it's gone; assert a non-owner context doesn't see the button. Extend to create/comment flows as those tickets land. Watch the route-coverage ratchet interplay (baseline re-derivation rule now documented in coverage-baseline.json).
Epic #705. No `e2e/playwright/*blog*` spec exists; coverage is only the generic route walk (`/blog` public, `/blog/create` auth). The owner-delete flow (angular #420) shipped with `data-testid="blog-entry-delete-button"` and the shared confirm dialog's testids, so the selectors are ready.
**Shape:** `authenticated-blog-delete.spec.ts` (fixtures import per e2e conventions): create a post as the e2e user → verify it renders on `/blog` → delete via the testid + `confirm-dialog-confirm` → verify it's gone; assert a non-owner context doesn't see the button. Extend to create/comment flows as those tickets land. Watch the route-coverage ratchet interplay (baseline re-derivation rule now documented in `coverage-baseline.json`).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Epic #705. No
e2e/playwright/*blog*spec exists; coverage is only the generic route walk (/blogpublic,/blog/createauth). The owner-delete flow (angular #420) shipped withdata-testid="blog-entry-delete-button"and the shared confirm dialog's testids, so the selectors are ready.Shape:
authenticated-blog-delete.spec.ts(fixtures import per e2e conventions): create a post as the e2e user → verify it renders on/blog→ delete via the testid +confirm-dialog-confirm→ verify it's gone; assert a non-owner context doesn't see the button. Extend to create/comment flows as those tickets land. Watch the route-coverage ratchet interplay (baseline re-derivation rule now documented incoverage-baseline.json).