test(e2e): add publish app happy path scenario#35503
Merged
Jingyi-Dify merged 3 commits intomainfrom Apr 23, 2026
Merged
Conversation
Jingyi-Dify
requested review from
Yeuoly,
crazywoola and
laipz8200
as code owners
dosubot
Bot
added
the
size:XS
…mmon
- Navigate to chatbot app by clicking from app list instead of bare /app/{id}
URL which never redirects to configuration page
- Move shared step definitions (app creation, app list navigation) to
common/app.steps.ts to prevent duplicate step errors when sibling
PR test/app-detail-navigation merges
lyzno1
previously approved these changes
Apr 23, 2026
- Change publish scenario from chat to workflow app: workflow publish
calls /apps/{id}/workflows/publish which has no model-config validation,
so it succeeds in CI without a configured LLM provider
- Add syncMinimalWorkflowDraft() API helper to seed a Start node before
opening the app, preventing the empty-canvas onboarding modal and
satisfying the frontend handleCheckBeforePublish start-node check
- Add 'a minimal workflow draft has been synced' Given step in common/
lyzno1
approved these changes
Apr 23, 2026
asukaminato0721
pushed a commit
to asukaminato0721/dify
that referenced
this pull request
Apr 24, 2026
fatelei
pushed a commit
that referenced
this pull request
Apr 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Fixes #<issue number>.Summary
What
e2e/features/apps/publish-app.featurewith a first-publish happy-path scenario tagged@apps @authenticated @coree2e/features/step-definitions/apps/publish-app.steps.tswith steps for API app creation, publish panel interaction, and publishedstate assertion
Why
The publish flow is a P0 business path with zero E2E coverage. Any regression in the Publish button or the publish API would be invisible
until users reported it in production. This scenario closes the "create → publish" minimum loop for chatbot apps using the real API, without
requiring a live LLM or any additional infrastructure.
Effect
--tags @corenow validates that the publish popover opens, the "Publish Update" button triggers the API, and the button transitions to"Published" state
Afterhook viacreatedAppIdsa {string} app has been created via APIandI navigate to the app detail pageare duplicated fromtest/app-detail-navigation(not yet merged); these should be consolidated into
common/when both PRs landScreenshots
Checklist
make lint && make type-check(backend) andcd web && pnpm exec vp staged(frontend) to appease the lint gods