[GitHub] [arrow-datafusion] HaoYang670 opened a new issue, #5512: Should we introduce property testing?

["HaoYang670 (via GitHub)" <gi...@apache.org>]

HaoYang670 opened a new issue, #5512:
URL: https://github.com/apache/arrow-datafusion/issues/5512

   **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
   This is actually not a feature, but a question or discussion.
   
   [Property testing ](https://en.wikipedia.org/wiki/Property_testing) is a useful tool for us to focus on the `properties` of objects, without caring about how testing data is generated.
   It is tasted like the formal verification.
   
   I am not sure whether we should consider adding it into the Datafusion. My first thought is that it can be applied to `Scalar`, `DataType`, `Expression` but may be not suitable for `Plan`. In another word, it is more suitable for unit test, maybe.
   
   
   There is no offical crate for property testing, unfortunately. I find some personal repos, such as:
   https://github.com/BurntSushi/quickcheck
   https://github.com/proptest-rs/proptest
    
   
   Actually, this is just a quick mind in my brain. I haven't found a practical way to implement it. But I'd like to hear your opinions.
   
   **Describe the solution you'd like**
   <!--
   A clear and concise description of what you want to happen.
   -->
   
   **Describe alternatives you've considered**
   <!--
   A clear and concise description of any alternative solutions or features you've considered.
   -->
   
   **Additional context**
   <!--
   Add any other context or screenshots about the feature request here.
   -->
   


-- 
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: github-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org