Automatic test case reduction
See original GitHub issueIt would be great to implement test case reduction strategies in SQLancer itself. The advantage of doing this in SQLancer, rather than an external tool like C-Reduce, is that we have all the information on whether a specific bug is still triggered (e.g., that two queries should yield the same result) and that the reduction can likely go further than when having an external interestingness test (e.g., since a predicate in the WHERE
condition of two queries can be reduced simultaneously).
See:
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
Test Case Reduction and Techniques to Follow | BrowserStack
Check out our guide on test case reduction techniques and learn how ... A large number of test suites are generated using Automation...
Read more >[2202.13823] Automatic Test-Case Reduction in Proof Assistants
In this paper, we describe insights about how test-case reduction is different in Coq than in traditional compilers.
Read more >bugpoint - automatic test case reduction tool - LLVM
It aims to reduce large test cases to small, useful ones. For more information on the design and inner workings of bugpoint, as...
Read more >Safe Test Case Reduction
a safe test case reduction technique that produces statically verifiable guards which encode the ... is true of all automated test generation techniques...
Read more >Everything You Ever Wanted To Know About Test-Case ...
Test -case reduction is a core part of a recently proposed algorithm to automatically fix some flaky tests. Deduplicate fuzzing bugs.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Maybe give
--test-nulls-first-last=false
a try?If you still have some time, the most useful thing would be to write the reduced test cases to a file, perhaps in a log-reduced directory adjacent to the current log directory.