alamb commented on code in PR #27198: URL: https://github.com/apache/datafusion/pull/27198#discussion_r4501302149
########## docs/source/contributor-guide/testing.md: ########## @@ -170,6 +170,42 @@ For local SQLite test instructions, see the [instructions in the documentation]. [instructions in the documentation]: https://github.com/apache/datafusion/tree/main/datafusion/sqllogictest#running-tests-sqlite [extended.yml]: https://github.com/apache/datafusion/blob/main/.github/workflows/extended.yml +## Rust Integration Tests + +There are several public interface tests for the DataFusion library in the [tests](https://github.com/apache/datafusion/tree/main/datafusion/core/tests) directory. + +You can run these tests individually using `cargo` as normal command such as + +```shell +cargo test -p datafusion --test parquet_integration +``` + +## Fuzz testing + +Fuzz testing generates random inputs and configurations, then checks that a property holds for every generated case. For example, an optimized operator should produce the same results as a reference implementation. + +### Fuzzing unit tests + +For fuzzing unit tests, such as tests for a single operator or an internal utility: + +- If the test is small (easy to set up and takes a few seconds), keep it as a unit test. +- If the test is large (requires a fuzzing driver and takes more than 10 seconds), it must implement the [`FuzzTest` trait][fuzz framework] and run through the [central fuzz-test entry point]. See the [spill-pool fuzzer] for a reference implementation. Review Comment: Do we want to make it a "must" ? Perhaps it would be better as an advisory ("should")? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
