There are 0 repository under flaky-tests topic.
A next-generation test runner for Rust.
:coffee: The one who serves a great Espresso
Track flaky tests in Sentry
Jest retry pattern for flaky E2E tests
A collection of JUnit 4 Rules for Android Developers 🔬
Run your processes in parallel mode with possibility to re-run them on fail
semgrep rules for flakiness, missed error handling, Lua antipatterns and pitfalls.
A fast and dirty checker based on libclang which detects non-deterministic iteration
Cypress plugin that helps skip/quarantine flaky tests dynamically
Official Unflakable Plugins for Python
This is the experimental package of paper entitled "On the use of test smells for prediction of flaky tests" that was submitted for publication in SAST 2021 - VI Brazilian Symposium on Systematic and Automated Software Testing.
Source code from the RubyConf 2023 talk about flaky tests entitled The Secret Ingredient by Alan Ridlehoover
Tool to identify and fix non-idempotent-outcome (NIO) flaky tests
Do you have some flaky tests? Are you using XUnit? Do you want to retry them a few times before considering them failures? Heck yeah brother (you should probably actually fix the test so it's not flaky, but sometimes you just don't have time!)
ICSME 2020 Artifact for: Shake It! Detecting Flaky Tests Caused by Concurrency with Shaker.
Official Unflakable Plugins for JavaScript
This is the experimental package of paper entitled "What is the Vocabulary of Flaky Tests? An Extended Replication" that was submitted for publication in ICPC 2021 - Replications and Negative Results (RENE).
Auto-ticket flaky tests in your rspec test suite
busted-flaky is a busted extension for handling flaky specs, heavily inspired on RSpec::Retry. Using busted-flaky any block can be retried a specified number of times until it succeeds.
Venera is an Android instrumentation that hooks into your testrunner and automatically gathers useful runtime information across test runs.
Divergent run a specific ava test case until it both passes and fails, then it to analyse the trace of both runs and provide the user with useful information, if the execution path or return values diverged from a passing and a failing run.
Divergent run a specific ava test case until it both passes and fails, then it to analyse the trace of both runs and provide the user with useful information, if the execution path or return values diverged from a passing and a failing run.
A GitHub Action for reporting test information from BuildPulse to a Discord channel
Example usage of rspec-sanity tests wrapper
Run "mvn test" multiple times and report slow / flaky tests