rspec-rails VS Pry

When starting a Rails project, you have a lot of decisions to make. Whether or not to write tests should not be one of them. The big decision is to use Minitest or Rspec. Both of those testing frameworks are great and provide everything you need to test a Rails application thoroughly.

RSpec

rspec-rails factory_bot_rails faker

Ruby testing with RSpec

After all requests have been added, we need to cover them using request specs to ensure that everything will work as expected in the future as well. To add specs, we will use the rspec-rails gem. Our plan is to cover the 4 HTTP request methods that have been added above:

as a beginner you can skip it, just focus on understanding Rails' philosophy and getting comfortable with it. However, make sure you remember to come back to unit testing later bc it's a mandatory skill for a Rails developer. Unit test can help you understand your project's specs thoroughly (assume its test coverage is more than 90%). I recommend learning RSpec instead of Rails' built-in testing tool (the one being used in the Rails tutorial iirc)

RSpec is a testing framework for Ruby that is widely used in the Ruby on Rails community. It allows developers to write and execute automated tests. RSpec promotes behavior-driven development (BDD) by providing a readable syntax for describing the expected behavior of the application.

This is where rswag comes in. It is an extension to rspec-rails for "describing and testing API operations".

that's surprising considering `pry`[1] is such an amazing debugger IMO.

[1] https://github.com/pry/pry

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:

For older versions: Pry Gem

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

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.

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.

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.