You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Run all sqllogictest, even if there are test failures in between.
When tests are run on CI, it will be more efficient if logictests can be run all the way through and report all failed cases.
Describe the solution you'd like
Does sqllogictest-rs have support for this, or does it need to be implemented on the user side? cc @xxchan
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.
The text was updated successfully, but these errors were encountered:
Does sqllogictest-rs have support for this, or does it need to be implemented on the user side?
Currently sqllogictest runner only has very thin wrappers (run_multi, run_file) over run (record). You need to implement custome testing logic. BTW, you may refer to sqllogictest-bin.
BTW, if you want to keep running later records in a file, that might be problematic, e.g., imagine a CREATE TABLE failed. But anyway you can implement any suitable policy using the basic building blocks.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Run all sqllogictest, even if there are test failures in between.
When tests are run on CI, it will be more efficient if logictests can be run all the way through and report all failed cases.
Describe the solution you'd like
Does sqllogictest-rs have support for this, or does it need to be implemented on the user side? cc @xxchan
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.
The text was updated successfully, but these errors were encountered: