emidab/lullalink
1
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Wiki Activity Actions

Set up CI pipeline enforcing analyze, tests, and coverage #12

New issue
Open
opened 2026-09-02 15:26:11 +02:00 by emidab · 0 comments
emidab commented 2026-09-02 15:26:11 +02:00
Owner
Copy link

Summary

Continuous integration and release readiness: ensure the project builds, tests pass headlessly, and artifacts can be produced on CI. This is the enforcement mechanism for the testing strategy.

What to do

  1. Set up Forgejo Actions workflow: analyze, test, build
  2. Enforce flutter analyze with zero warnings as a gate
  3. Run the full headless test suite (unit/widget/golden) on every PR/merge
  4. Build/debug-APK artifact for each supported platform where feasible
  5. Add a Codecov or equivalent coverage gate

Acceptance criteria

  • CI runs analyzer cleanly (zero warnings)
  • Full test suite runs on CI and blocks merge on failure
  • Coverage reported and gate configured
  • Build artifacts produced per PR/merge (at minimum for the primary platform)

Notes

  • Depends on the testing-strategy issue (the harness this enforces)
  • Keep the pipeline parallelizable and fast
## Summary Continuous integration and release readiness: ensure the project builds, tests pass headlessly, and artifacts can be produced on CI. This is the enforcement mechanism for the testing strategy. ## What to do 1. Set up Forgejo Actions workflow: analyze, test, build 2. Enforce `flutter analyze` with zero warnings as a gate 3. Run the full headless test suite (unit/widget/golden) on every PR/merge 4. Build/debug-APK artifact for each supported platform where feasible 5. Add a Codecov or equivalent coverage gate ## Acceptance criteria - [ ] CI runs analyzer cleanly (zero warnings) - [ ] Full test suite runs on CI and blocks merge on failure - [ ] Coverage reported and gate configured - [ ] Build artifacts produced per PR/merge (at minimum for the primary platform) ## Notes - Depends on the testing-strategy issue (the harness this enforces) - Keep the pipeline parallelizable and fast
emidab added this to the v0.1 — MVP: P2P baby monitor milestone 2026-09-02 15:28:42 +02:00
emidab added the
area: setup
area: testing
size: s
priority: high
 labels 2026-09-02 15:28:43 +02:00
emidab added a new dependency 2026-09-02 15:35:49 +02:00
#2 Establish canonical testing strategy with headless CI
emidab added a new dependency 2026-09-02 15:35:50 +02:00
#1 Initialize Flutter project with clean architecture
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
area: child

   
area: networking

   
area: parent

   
area: setup

   
area: testing

   
area: ui

   
priority: high

   
priority: low

   
priority: medium

   
size: l

21-34 points

  
size: m

8-13 points

  
size: s

3-5 points

  
size: xl

55-89 points

  
size: xs

1-2 points

No labels
area: child
area: networking
area: parent
area: setup
area: testing
area: ui
priority: high
priority: low
priority: medium
size: l
size: m
size: s
size: xl
size: xs
Milestone
Clear milestone
No items
No milestone
v0.1 — MVP: P2P baby monitor
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#1 Initialize Flutter project with clean architecture
emidab/lullalink
#2 Establish canonical testing strategy with headless CI
emidab/lullalink
Reference: emidab/lullalink#12
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?