fix: tighten scheduled execution E2E coverage by Syroxivoss · Pull Request #11986 · appwrite/appwrite · GitHub
Skip to content

fix: tighten scheduled execution E2E coverage#11986

Open
Syroxivoss wants to merge 2 commits intoappwrite:1.9.xfrom
Syroxivoss:fix-11984-scheduled-execution-e2e-coverage
Open

fix: tighten scheduled execution E2E coverage#11986
Syroxivoss wants to merge 2 commits intoappwrite:1.9.xfrom
Syroxivoss:fix-11984-scheduled-execution-e2e-coverage

Conversation

@Syroxivoss
Copy link
Copy Markdown

What does this PR do?

Adds end-to-end coverage for the createExecution scheduledAt boundary rules without changing production behavior.

This updates the scheduled execution E2E test to cover the contract described in the issue more explicitly:

  • verifies the successful async scheduled execution path returns the expected schedule trigger and scheduledAt value
  • verifies scheduled executions are rejected when async=false
  • verifies minute-precision scheduledAt values that are less than 1 minute ahead are rejected with the expected validation message

The goal here is to protect the existing API behavior against regression, not to change runtime behavior.

Test Plan

  • Verified the updated test file is clean in editor diagnostics.

  • Full Docker/PHP execution could not be run in this environment because the required CLIs were unavailable.

  • Recommended validation command in a full local Appwrite environment:

    docker compose exec appwrite test tests/e2e/Services/FunctionsSchedule/FunctionsScheduleTest.php --filter=ScheduledExecution

Related PRs and Issues

Closes #11984

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 23, 2026

Comment thread tests/e2e/Services/FunctionsSchedule/FunctionsScheduleTest.php Outdated
Comment thread tests/e2e/Services/FunctionsSchedule/FunctionsScheduleTest.php
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add E2E coverage for createExecution scheduledAt async and 1-minute boundary rules

1 participant