Capybara
Pry
Capybara | Pry | |
---|---|---|
21 | 36 | |
9,971 | 6,729 | |
0.3% | 0.4% | |
7.9 | 7.2 | |
about 1 month ago | 27 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.
Capybara
-
16 Best Ruby Frameworks For Web Development [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
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
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
-
Using Capybara to test responsive code
Engineering at Aha! focuses on using and improving the Capybara test framework. We have added many helpers and additional functionality to make working with Capybara easy. Testing at mobile widths is another chance to improve our testing tooling. Here is the incremental approach that we used to add mobile testing helpers.
-
Minitest vs. RSpec in Rails
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?
-
Testing Strategies For Microservices
We can write component tests with any language or framework, but the most popular ones are probably Cucumber and Capybara.
-
From partials to ViewComponents: writing reusable front-end code in Rails
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.
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.
-
Validating Views with Capybara Queries
When you write a system test (or, as we prefer, a system spec) with Ruby on Rails, you're exercising the whole stack from the point of view of the user. So, naturally, you have to do things like make sure that certain elements are on the page and work as you expect when you click on then, type in them, and drag them around. Capybara works exceedingly well for this, giving you a lovely API for querying HTML.
Pry
- The File Filesystem
-
Ruby 3.3
that's surprising considering `pry`[1] is such an amazing debugger IMO.
[1] https://github.com/pry/pry
-
Enhancing development with REPLs - A practical guide
All of my recent tutorials and projects were primarily managed using the default Ruby REPL, irb, and I must say it's been nothing short of amazing. However, what ultimately prompted me to switch to Pry was its offering of better defaults. But what exactly does that mean? Let me demonstrate:
- Free/low cost IDE recommendations please. :)
-
Debugging Help
For older versions: Pry Gem
-
Anyone else working through Michael Hartl's Learn Enough RoR Series that might be able to help me with a failing unit test?
To do that, I would install `pry` into your rails project and then use it look around right before your test fails.https://github.com/pry/pry
- I made a tool to help cleanly copy & paste code from irb/pry sessions
-
shell-maker: Make your own shell in 15 lines of elisp (batteries included)
This means I can be editing a shell script and easily inject arbitrary regions into a shell buffer for immediate testing (point never leaves the window where I am editing, and I can view the shell output in an adjacent window). This is similar to what Robe does with Pry within an inferior Ruby process using comint.
-
Building GitHub with Ruby on Rails
https://pry.github.io/ - also a lot of features from Pry have made it into the default IRB these days, but I still use pry. I don't know the equivalent commands in IRB.
-
Is parallel threading never going to be a thing?
For debugging, while not multi-threaded, to my knowledge, is the pry gem for debugging. There are a few different flavors, for instance, my favorite is pry-byebug.
What are some alternatives?
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
Byebug - Debugging in Ruby 2
Aruba - Test command-line applications with Cucumber-Ruby, RSpec or Minitest.
irbtools - Improvements for Ruby's IRB console 💎︎
shoulda-matchers - Simple one-liner tests for common Rails functionality
Hirb - A mini view framework for console/irb that's easy to use, even while under its influence. Console goodies include a no-wrap table, auto-pager, tree and menu.
Emoji-RSpec - Custom Emoji Formatters for RSpec
debug - Debugging functionality for Ruby
Cucumber - A home for issues that are common to multiple cucumber repositories
pry-remote - Connect to Pry remotely
Bacon - a small RSpec clone
Amazing Print - Pretty print your Ruby objects with style -- in full color and with proper indentation