retest
bundleup
retest | bundleup | |
---|---|---|
6 | 1 | |
121 | 189 | |
- | - | |
7.4 | 7.3 | |
about 2 months ago | 4 days ago | |
Ruby | Ruby | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
retest
-
Minitest, we've been doing it wrong?
Whatever you choose Retest (a gem I maintain) will acknowledge both naming conventions out of the box to increase the number of compatible Ruby projects. This is done in release 1.10.0. For example, you can now use Retest with Puma.
-
For those using VSCode, is there a faster way to run "rspec" on the file shown in my active tab (a _spec.rb file)?
I created a gem: Retest which works on the terminal. A bit like Guard without any setup. The gem is smart enough to find the correct file to test after you save any.rb file.
-
Is using the gem Guard still state of the art in TDD with Ruby?
I use retest. It works on every standard Ruby projects with no setup (understand no .Guardfile or Gemfile update). If you follow rspec, rails, rake or ruby standard file structure you get running in less than a minute. As a contractor I can checkout any repo and start TDD without caring about the repo setup. I use it even when Guard is already installed because the experience is consistent across all projects. It also has a —diff option that runs only spec files relevant from the diffs with another branch to run a final check before creating a pull request and triggering the whole test suite on CI.
-
Any love for MiniTest?
But whatever the project I’m working on is, I always try using retest https://github.com/AlexB52/retest for awesome refactoring and TDD because it works with both Minitest and RSpec out of the box. Sorry for the shameless promotion.
-
Can I run guard without adding it to a project?
Hi, I have created a gem called retest that helps you run specs after a file change without adding any configuration files to a repo. I created it for the specific reason you’re mentioning as I work in a consultancy. It is supposed to be dev centric and works with any ruby projects. I use it while working or refactoring. It might suits you, have a look
-
Refactoring in Ruby
A great book by Sandi Metz is 99 bottles of OOP in Ruby where she explains heaps about refactoring. One of the best book I have read. I know you asked for article or videos but if you have time, it takes a day or two to read. I made a gem to help people refactor the same way she describes in the book. It will speed up your feedback loop when refactoring: retest
bundleup
-
Best practice: should I specify versions in Gem file?
To update your bundle I would suggest bundleup which does bundle update + show what's updated + what's outdated (even those due to version constraints in Gemfile)
What are some alternatives?
entr - Run arbitrary commands when files change
jektex - A Jekyll plugin for blazing-fast server-side cached LaTeX rendering, with support for macros. Enjoy the comfort of LaTeX and Markdown without cluttering your site with bloated JavaScript.
minitest - minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking.
Discourse - A platform for community discussion. Free, open, simple.
Puma - A Ruby/Rack web server built for parallelism
Jekyll - :globe_with_meridians: Jekyll is a blog-aware static site generator in Ruby
rerun - Restarts an app when the filesystem changes. Uses growl and FSEventStream if on OS X.
Ruby on Rails - Ruby on Rails
vim-test - Run your tests at the speed of thought
bundler - Bundler support for Capistrano 3.x
Rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide. [Moved to: https://github.com/rubocop/rubocop]
rubygems - Library packaging and distribution for Ruby.