Capybara VS RailsAdmin

Compare Capybara vs RailsAdmin and see what are their differences.

Capybara

Acceptance test framework for web applications (by teamcapybara)

RailsAdmin

RailsAdmin is a Rails engine that provides an easy-to-use interface for managing your data (by railsadminteam)
Our great sponsors
  • PopRuby - Clothing and Accessories for Ruby Developers
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
Capybara RailsAdmin
20 9
9,946 7,849
0.3% 0.2%
7.7 7.5
1 day ago 27 days ago
Ruby Ruby
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

Capybara

Posts with mentions or reviews of Capybara. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-11.
  • 16 Best Ruby Frameworks For Web Development [2024]
    6 projects | dev.to | 11 Mar 2024
    Cuba takes help from a lot of other technologies to bring the best of everything. For example, the responses in Cuba are the optimized version of the Rack responses. The templates are integrated via Tilt and testing via Cutest and Capybara.
  • đź©° Scheduling automated tests
    4 projects | dev.to | 1 Sep 2023
    I am going to use a browser based testing tool called Playwright (But you could use Capybara, or Selenium WebDriver etc.).
  • Building GitHub with Ruby on Rails
    11 projects | news.ycombinator.com | 7 Apr 2023
    Even as a much smaller team, building Heii On-Call [0] as a lightweight alerting/monitoring/on-call rotations SaaS based on Ruby on Rails has basically been a pleasure!

    And as the article highlights, perhaps the key reason for smooth deployments and upgrades is that the CI testing story is so, so good: RSpec [1] plus Capybara [2] for us. That means we have decently extensive tests of just about all behavior. The few small Rails and Ruby upgrades we've done have gone quite smoothly and confidently, with usually just a few non-Rails gem dependencies needing to be manually updated as well.

    The "microservices" story is where we've pulled in the Crystal programming language [3] to great effect. After dabbling with Go and Rust, we've found that Crystal is truly a breath of fresh air. Crystal powers the parts of Heii On-Call that need to be fast and low-RAM, specifically the inbound API https://api.heiioncall.com/ and the outbound HTTP(S) prober background processes. I've ported some shared utility classes from Ruby to Crystal almost completely by just copy-and-pasting ___.rb to ___.cr; porting the tests for those classes was far more onerous than porting the class code itself. (Perhaps another point of evidence toward the superiority of RoR's testing story...)

    The front-end story is nice but just a bit weaker. Using Hotwire / Turbo successfully, but I have an open PR to fix a fairly obvious stale cache bug in Turbo [4] that has been sitting unloved for nearly a month, despite other users reporting the same issue. I'm hopeful that it will get merged in the next release, but definitely less active than the backend side.

    For me, the key conclusion is that the excellent Ruby on Rails testing story is what enables everything to go a lot more smoothly and have such a strong foundation. I'd be curious if any GitHubbers can talk more about whether they too are using Rspec+Capybara or something else? Are there internal guidelines for test coverage?

    [0] https://heiioncall.com/

    [1] https://rspec.info/

    [2] https://github.com/teamcapybara/capybara

    [3] https://crystal-lang.org/

    [4] https://github.com/hotwired/turbo/pull/895

  • Minitest vs. RSpec in Rails
    3 projects | dev.to | 5 Oct 2022
    Since the Capybara library drives the underlying tests, Minitest also has the same syntax.
  • Is it a common practice to test JS code in a browser instead of Node.js?
    2 projects | /r/AskProgramming | 12 Sep 2022
  • From partials to ViewComponents: writing reusable front-end code in Rails
    11 projects | dev.to | 3 Jun 2022
    The nice thing about partial templates is that templates are unit-testable with View specs (or similarly in Minitest) and the rendered output can even be verified using Capybara matchers.
  • Tip: if you're changing all your form_for to form_with, take the opportunity to make sure all forms are being tested.
    2 projects | /r/rails | 11 Apr 2022
    To piggyback: This would be a type of browser test, so you would want to use something like Cypress (https://github.com/testdouble/cypress-rails) or Capybara (https://github.com/teamcapybara/capybara). RSpec has a good integration with Capybara. Cypress is JS-based so it will require some additional config.
  • How to use undocumented web APIs
    10 projects | news.ycombinator.com | 10 Mar 2022
  • Don't make me think, or why I switched to Rails from JavaScript SPAs
    22 projects | news.ycombinator.com | 4 Feb 2022
  • The Benefits of Acceptance Testing
    4 projects | dev.to | 18 Nov 2021
    For instance, the acceptance test above requires a log in routine. Here's where the expressive power of a DSL like Capybara manifests:

RailsAdmin

Posts with mentions or reviews of RailsAdmin. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-10-28.
  • Ask HN: Why aren't Django Admin style dashboards popular in other frameworks?
    6 projects | news.ycombinator.com | 28 Oct 2023
    Like most things, it's probably a combination of things.

    The Django Admin existed before Django publicly existed. That meant that once anyone started using Django they knew that they should constrain their use of Django in certain ways so that the Django Admin would work with their usage. Features that would be added to Django would be built with the Django Admin in mind.

    Many tools like Flask or FastAPI don't have an opinionated model layer like Django. Without that, you can't really create an admin interface programatically. People could be storing their data in any sort of fashion anywhere. How would one build an admin system for something like Flask or FastAPI where there's no convention around how people set up data access? A lot of frameworks out there don't tell you "access your data in this way" or "this is how users will be authenticated." Without those two things, it's hard to really create an admin system.

    There are similar systems available for some frameworks, but since they aren't part of the core framework, they don't get the same attention. Someone creates it, but it doesn't have the kind of community buy-in that sustains it. One of the odd things about Django is that the admin system is under `django.contrib` which indicated that they didn't intend for it to be in the core of Django forever, but that's not really how `django.contrib` ended up. It continued to be a core part of Django maintained as part of the framework.

    Like I said, there are admin dashboards available in other frameworks like RailsAdmin (https://github.com/railsadminteam/rails_admin) or Core Admin for .NET (https://github.com/edandersen/core-admin) and I'm sure there's more. However, both Rails and .NET provide most of what Django provides (and a lot more than most frameworks). Rails and .NET both have a default data access ORM that a majority of people using those frameworks tend to use. .NET has built-in authentication/authorization so the admin can work off that. Rails doesn't have auth, but RailsAdmin uses some plugins.

  • From partials to ViewComponents: writing reusable front-end code in Rails
    11 projects | dev.to | 3 Jun 2022
    We briefly considered migrating to a full-grown Rails admin interface, such as ActiveAdmin, RailsAdmin, Administrate or Avo. We especially liked Avo which is built on a very modern stack similar to ours (Tailwind + Hotwire + ViewComponents). In the end, we didn’t go this route as we found some of the options a bit too restrictive (even though Avo is very flexible) and we did not feel like trying to amend it to our needs. For example, Avo renders forms in a 1-field-per-row layout while we wanted something more similar to the Tailwind UI Stacked form layout. Nevertheless, we found a great deal of inspiration in the Avo code and its design principles.
  • railstart-niceadmin support more features
    37 projects | /r/rails | 16 Feb 2022
    - [rails_admin](https://github.com/railsadminteam/rails_admin)
  • railstart-niceadmin release now!Backend management system based on Bootstrap 5 and NiceAdmin and Rails 7
    29 projects | dev.to | 27 Jan 2022
    rails_admin
  • Admin Framework for Rails
    10 projects | /r/rails | 10 Nov 2021
    https://github.com/railsadminteam/rails_admin is very popular and i find it very easy to use.
  • 🤷‍♀️ The easiest way to monitor your app in production is email?
    3 projects | dev.to | 19 Oct 2021
    It's really helpful to have a way to track what's going on with your application in production, things like: number of user sign ups, status of user accounts, number of X new database entries etc. Out of the box dashboards like Rails Admin are great but only go so far, eventually you will want significant customizations.
  • An Easy Admin Panel - Rails 6
    2 projects | dev.to | 28 May 2021
    Having an admin panel in your Rails application is honestly, to me, the best thing to do when it comes to keeping track of your users and giving them permissions. Finding out how to have an admin panel though, that was tough, mainly because I wasn’t searching for the right thing. The rails_admin gem, so simple but can control so much! The installation and usage is very simple depending on what you are trying to use it on. I should probably tell you, I am using devise with the user having a boolean attribute called admin.
  • Ask HN: What is an easy way to create web UIs as a back end dev/data scientist?
    2 projects | news.ycombinator.com | 13 Mar 2021
    Check out Retool: https://www.ycombinator.com/companies/1564

    A wswig for internal UI/dashboards has a lot of value for companies that don't have a dedicated internal tools team.

    My company had an internal tools teams at one point but it got killed because of other business priorities.

    We use https://github.com/sferik/rails_admin, that still requires development time and frontend knowledge, but the framework is terrible.

    https://marmelab.com/react-admin/ is much better but also required development time and frontend knowledge.

What are some alternatives?

When comparing Capybara and RailsAdmin you can also consider the following projects:

ActiveAdmin - The administration framework for Ruby on Rails applications.

Administrate - A Rails engine that helps you put together a super-flexible admin dashboard.

Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

Trestle - A modern, responsive admin framework for Ruby on Rails

motor-admin-rails - Low-code Admin panel and Business intelligence Rails engine. No DSL - configurable from the UI. Rails Admin, Active Admin, Blazer modern alternative.

Aruba - Test command-line applications with Cucumber-Ruby, RSpec or Minitest.

shoulda-matchers - Simple one-liner tests for common Rails functionality

Emoji-RSpec - Custom Emoji Formatters for RSpec

Avo - Build Ruby on Rails apps 10x faster

Cucumber - A home for issues that are common to multiple cucumber repositories

Bacon - a small RSpec clone

stimulus-use - A collection of composable behaviors for your Stimulus Controllers