Skip to content

Add documentation for Run extended tests command #15463

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 28, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/source/contributor-guide/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,8 +79,15 @@ than the standard test suite and add important test coverage such as that the
code works when there are hash collisions as well as running the relevant
portions of the entire [sqlite test suite].

You can run the extended tests on any PR by leaving the following comment (see [example here]):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so to run extended tests, is it optional or is it to rerun failed tests?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Normally extended tests don't run on PRs, only after merges to main

If you want to run extended tests on a PR prior to merge, now you by leaving a Run extended test comment on the PR


```
Run extended tests
```

[extended.yml]: https://github.com/apache/datafusion/blob/main/.github/workflows/extended.yml
[sqlite test suite]: https://www.sqlite.org/sqllogictest/dir?ci=tip
[example here]: https://github.com/apache/datafusion/pull/15427#issuecomment-2759160812

## Rust Integration Tests

Expand Down