docs(app): record merged schedule form checks
This commit is contained in:
@@ -102,8 +102,8 @@ dart format lib/features/schedules/ui/editor test/features/schedules/ui/editor \
|
||||
tool/schedule_editor_probe_app.dart # clean
|
||||
flutter analyze # No issues found!
|
||||
flutter test test/features/schedules # 69 passed
|
||||
flutter test # 686 passed before the
|
||||
# main merge, 687 after
|
||||
flutter test # 686 before merging main;
|
||||
# 704 on the merged tree
|
||||
flutter build web # ✓ Built build/web
|
||||
flutter build web -t tool/schedule_editor_probe_app.dart \
|
||||
-o build/schedule_editor_probe_web # ✓ Built
|
||||
@@ -112,10 +112,11 @@ OPENCODE_ARTIFACT_DIR=…/78/public/s1-form-captures \
|
||||
node tool/schedule_editor_probe.mjs # all checks passed
|
||||
```
|
||||
|
||||
After merging `main` into `flutter/schedule-form` (conflict-free; the incoming
|
||||
commit only touches templates), the same checks were re-run on the merged tree:
|
||||
`flutter analyze` clean, 69 schedules tests, 687 whole-app tests, `flutter build
|
||||
web`, and all six fixture probe checks with no page errors.
|
||||
After merging the current `main` into `flutter/schedule-form` (conflict-free;
|
||||
the incoming work was unrelated template and chat-composer state changes), the
|
||||
same checks were re-run on the merged tree: `flutter analyze` clean, 69 schedules
|
||||
tests, 704 whole-app tests, `flutter build web`, and all six fixture probe checks
|
||||
with no page errors.
|
||||
|
||||
Browser checks that actually ran in real headless Chrome against the fixture:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user