0.0
No commit activity in last 3 years
No release in over 3 years
Flaky stats will rerun broken tests from your parallel tests and if they pass then they must be flaky so it records them.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.14
>= 0
~> 10.0
~> 3.0
= 0.8.1
 Project Readme

FlakyStats

Collects broken tests from a parallel failing test log, uses them to rerun the flaky tests and if they pass whilst running them on their own add them to the flaky_stats.log file.

At the end of the tests we can display a flaky stats summary which should display the top flaky tests in order of the most flakiest.

Installation

Add this line to your application's Gemfile:

gem 'flaky_stats'

And then execute:

$ bundle

Or install it yourself as:

$ gem install flaky_stats

Usage

$ rake parallel:rerun

Environment variables

Use the following to skip running flaky tests after parallel

NO_FLAKY=true rake parallel:all

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/map7/flaky_stats.

TODO

  • Create a rake task to show the flaky test summary
  • Get working with more than parallel tests
  • Test on CI environments
  • Do away with the ',1' on the end of our data This 1 on the end of each data line in the file is for a quick calculation, if this can be done without this then we can simplify our data.
  • More tests

Ref

http://blog.nathanhumbert.com/2010/02/rails-3-loading-rake-tasks-from-gem.html