How do I change the progress bar format in Fuubar?

Set the 'fuubar_progress_bar_options' in your RSpec configuration, using the format option from ruby-progressbar. For example, add config.fuubar_progress_bar_options = { :format => 'Custom %p%%' } in spec_helper.rb, as shown in the README.

Does Fuubar slow down RSpec test runs?

Fuubar adds minimal overhead since it primarily updates a progress bar; however, enabling auto-refresh might cause slight performance hits due to frequent updates, especially in very large test suites.

Fuubar vs RSpec's default formatter: which is better for debugging?

Fuubar provides immediate failure feedback with a progress bar, ideal for spotting issues quickly, while RSpec's default formatter offers detailed per-test output, better for step-by-step debugging without visual distractions.

How to integrate Fuubar with Pry for debugging?

Add hooks in your spec_helper to disable auto-refresh during Pry sessions, as described in the README. Use Pry.config.hooks to toggle RSpec.configuration.fuubar_auto_refresh before and after debugging.

Can Fuubar hide skipped tests in the output?

Yes, set config.fuubar_output_pending_results = false in your RSpec configuration to suppress summaries of pending or skipped tests, keeping the output cleaner during test runs.

Why isn't my Fuubar bar updating in real-time?

Ensure auto-refresh is enabled with config.fuubar_auto_refresh = true. If it's still not updating, check for debugger interference or ensure you're not in a mode that disables refresh, like during Pry sessions without proper hooks.

Open-Awesome

Fuubar

MITRuby

An instafailing RSpec formatter that replaces traditional output with a progress bar for real-time test feedback.

Visit Website GitHub

962 stars67 forks0 contributors

What is Fuubar?

Fuubar is an RSpec formatter that replaces the traditional test output with a progress bar that immediately shows failing tests. It provides real-time feedback during test execution, allowing developers to see test progress and failures as they happen rather than waiting for the test run to complete.

Target Audience

Ruby developers using RSpec for testing who want better visual feedback during test execution, particularly those working on larger test suites where immediate failure identification is valuable.

Value Proposition

Developers choose Fuubar because it provides immediate visual feedback about test failures through its instafailing progress bar, offers extensive customization options, and integrates well with debugging tools while maintaining compatibility with standard RSpec workflows.

Overview

The instafailing RSpec progress bar formatter

Use Cases

Best For

Getting immediate visual feedback on failing RSpec tests
Tracking progress of large RSpec test suites with real-time ETA
Customizing RSpec output with progress bars and custom formats
Improving developer experience during continuous integration test runs
Debugging RSpec tests while maintaining progress bar functionality
Teams wanting cleaner test output by suppressing pending spec summaries

Not Ideal For

CI/CD pipelines that parse RSpec's standard dot/letter output for automated test reporting
Projects using testing frameworks other than RSpec, such as Minitest or Cucumber
Developers who need verbose, per-test output logs for immediate debugging without a progress bar overlay

Pros & Cons

Pros

Immediate Failure Feedback

Instafailing progress bar shows test failures as they occur, unlike traditional formatters that only report at the end, based on the README's emphasis on real-time visual feedback.

Highly Customizable Bar

Leverages ruby-progressbar for extensive formatting options, allowing custom formats and refresh rates, as detailed in the advanced usage section for personalized output.

Clean Output Control

Configurable option to hide pending or skipped test summaries, reducing noise for teams with many pending specs, mentioned in the pending spec control feature.

Real-Time ETA Updates

Optional auto-refresh mode updates the progress bar every second, providing accurate time estimates during long test runs, as described in the auto-refresh section.

Debugger Integration

Built-in support for Pry with hooks to disable auto-refresh, and workarounds for Byebug, ensuring compatibility with common debugging tools, per the debugger integration section.

Cons

Debugger Compatibility Issues

Auto-refresh feature conflicts with debuggers; Byebug lacks hooks requiring manual disabling, and Pry setup needs additional configuration, as admitted in the undesirable effects section.

Configuration Complexity

Customizing the progress bar requires understanding ruby-progressbar's options, adding a layer of complexity for simple tweaks compared to plug-and-play formatters.

Ecosystem Limitation

Only compatible with RSpec, making it useless for projects using other testing frameworks, an inherent restriction not addressed by the project.

Frequently Asked Questions

Related Projects

faker

A library for generating fake data such as names, addresses, and phone numbers.

Stars11,599

Forks3,166

Last commit2 days ago

Capybara

Acceptance test framework for web applications

Stars10,156

Forks1,469

Last commit15 days ago

factory_bot

A library for setting up Ruby objects as test data.

Stars8,193

Forks2,565

Last commit16 days ago

VCR

Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests.

Stars6,049

Forks506

Last commit1 month ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub