home.social

#rspec — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #rspec, aggregated by home.social.

  1. ICYMI, I updated my RSpec testing book for Rails 8.1 and Ruby 4.0! Learn to test—and think about tests—the way I did, through a hands-on, full-stack approach. Minimal theory and dogma—just a straightforward, practical, and time-tested guide to software testing

    I'm running a launch discount through April for $9 (regularly $19), and as always, it's a free update if you got your copy through Leanpub.

    Please pass along; sharing is caring 🤗

    #RubyOnRails #RSpec

    leanpub.com/everydayrailsrspec

  2. ICYMI, I updated my RSpec testing book for Rails 8.1 and Ruby 4.0! Learn to test—and think about tests—the way I did, through a hands-on, full-stack approach. Minimal theory and dogma—just a straightforward, practical, and time-tested guide to software testing

    I'm running a launch discount through April for $9 (regularly $19), and as always, it's a free update if you got your copy through Leanpub.

    Please pass along; sharing is caring 🤗

    #RubyOnRails #RSpec

    leanpub.com/everydayrailsrspec

  3. ICYMI, I updated my RSpec testing book for Rails 8.1 and Ruby 4.0! Learn to test—and think about tests—the way I did, through a hands-on, full-stack approach. Minimal theory and dogma—just a straightforward, practical, and time-tested guide to software testing

    I'm running a launch discount through April for $9 (regularly $19), and as always, it's a free update if you got your copy through Leanpub.

    Please pass along; sharing is caring 🤗

    #RubyOnRails #RSpec

    leanpub.com/everydayrailsrspec

  4. ICYMI, I updated my RSpec testing book for Rails 8.1 and Ruby 4.0! Learn to test—and think about tests—the way I did, through a hands-on, full-stack approach. Minimal theory and dogma—just a straightforward, practical, and time-tested guide to software testing

    I'm running a launch discount through April for $9 (regularly $19), and as always, it's a free update if you got your copy through Leanpub.

    Please pass along; sharing is caring 🤗

    #RubyOnRails #RSpec

    leanpub.com/everydayrailsrspec

  5. ICYMI, I updated my RSpec testing book for Rails 8.1 and Ruby 4.0! Learn to test—and think about tests—the way I did, through a hands-on, full-stack approach. Minimal theory and dogma—just a straightforward, practical, and time-tested guide to software testing

    I'm running a launch discount through April for $9 (regularly $19), and as always, it's a free update if you got your copy through Leanpub.

    Please pass along; sharing is caring 🤗

    #RubyOnRails #RSpec

    leanpub.com/everydayrailsrspec

  6. #CoPilot obviously doesn't know how to do a proper test setup using #RSpec's context blocks in a "given-when-then" style. It hurts to read this stuff.

    #AI #ruby

  7. #CoPilot obviously doesn't know how to do a proper test setup using #RSpec's context blocks in a "given-when-then" style. It hurts to read this stuff.

    #AI #ruby

  8. #CoPilot obviously doesn't know how to do a proper test setup using #RSpec's context blocks in a "given-when-then" style. It hurts to read this stuff.

    #AI #ruby

  9. #CoPilot obviously doesn't know how to do a proper test setup using #RSpec's context blocks in a "given-when-then" style. It hurts to read this stuff.

    #AI #ruby

  10. #CoPilot obviously doesn't know how to do a proper test setup using #RSpec's context blocks in a "given-when-then" style. It hurts to read this stuff.

    #AI #ruby

  11. ⚡ From ~30 minutes to ~2 minutes: how a Rails team achieved ultra-fast CI — without rewriting tests.

    Parallel RSpec done right, smart workload balancing, PostgreSQL on tmpfs (RAM), and even reconsidering cloud vs physical hardware.

    Inspired by a Kaigi on Rails 2025 talk 🇯🇵

    🔗 rubystacknews.com/2026/02/18/%

    #Ruby #Rails #CI #RSpec #DevOps #Performance #KaigiOnRails

  12. ⚡ From ~30 minutes to ~2 minutes: how a Rails team achieved ultra-fast CI — without rewriting tests.

    Parallel RSpec done right, smart workload balancing, PostgreSQL on tmpfs (RAM), and even reconsidering cloud vs physical hardware.

    Inspired by a Kaigi on Rails 2025 talk 🇯🇵

    🔗 rubystacknews.com/2026/02/18/%

    #Ruby #Rails #CI #RSpec #DevOps #Performance #KaigiOnRails

  13. ⚡ From ~30 minutes to ~2 minutes: how a Rails team achieved ultra-fast CI — without rewriting tests.

    Parallel RSpec done right, smart workload balancing, PostgreSQL on tmpfs (RAM), and even reconsidering cloud vs physical hardware.

    Inspired by a Kaigi on Rails 2025 talk 🇯🇵

    🔗 rubystacknews.com/2026/02/18/%

    #Ruby #Rails #CI #RSpec #DevOps #Performance #KaigiOnRails

  14. ⚡ From ~30 minutes to ~2 minutes: how a Rails team achieved ultra-fast CI — without rewriting tests.

    Parallel RSpec done right, smart workload balancing, PostgreSQL on tmpfs (RAM), and even reconsidering cloud vs physical hardware.

    Inspired by a Kaigi on Rails 2025 talk 🇯🇵

    🔗 rubystacknews.com/2026/02/18/%

    #Ruby #Rails #CI #RSpec #DevOps #Performance #KaigiOnRails

  15. ⚡ From ~30 minutes to ~2 minutes: how a Rails team achieved ultra-fast CI — without rewriting tests.

    Parallel RSpec done right, smart workload balancing, PostgreSQL on tmpfs (RAM), and even reconsidering cloud vs physical hardware.

    Inspired by a Kaigi on Rails 2025 talk 🇯🇵

    🔗 rubystacknews.com/2026/02/18/%

    #Ruby #Rails #CI #RSpec #DevOps #Performance #KaigiOnRails

  16. Hi #ruby community I'm looking for other recommendation here codeberg.org/codeDude/romodoro

    I''m not sure how to test this with #Rspec

    basically the intention is test if the duration is for example 2 seconds the countdown spend 2 seconds.

    Could you gimme ideas please?

    #rails #coding #programming #unitTest #softwareDevelopment

  17. Hi #ruby community I'm looking for other recommendation here codeberg.org/codeDude/romodoro

    I''m not sure how to test this with #Rspec

    basically the intention is test if the duration is for example 2 seconds the countdown spend 2 seconds.

    Could you gimme ideas please?

    #rails #coding #programming #unitTest #softwareDevelopment

  18. Hi #ruby community I'm looking for other recommendation here codeberg.org/codeDude/romodoro

    I''m not sure how to test this with #Rspec

    basically the intention is test if the duration is for example 2 seconds the countdown spend 2 seconds.

    Could you gimme ideas please?

    #rails #coding #programming #unitTest #softwareDevelopment

  19. Hi #ruby community I'm looking for other recommendation here codeberg.org/codeDude/romodoro

    I''m not sure how to test this with #Rspec

    basically the intention is test if the duration is for example 2 seconds the countdown spend 2 seconds.

    Could you gimme ideas please?

    #rails #coding #programming #unitTest #softwareDevelopment

  20. Hi #ruby community I'm looking for other recommendation here codeberg.org/codeDude/romodoro

    I''m not sure how to test this with #Rspec

    basically the intention is test if the duration is for example 2 seconds the countdown spend 2 seconds.

    Could you gimme ideas please?

    #rails #coding #programming #unitTest #softwareDevelopment

  21. @kerrick And #RSpec.

    Whenever I have to use anything other than #Ruby, I am immediately reminded of how every single testing framework is miles, no, light-years behind RSpec.

  22. @kerrick And #RSpec.

    Whenever I have to use anything other than #Ruby, I am immediately reminded of how every single testing framework is miles, no, light-years behind RSpec.

  23. @kerrick And #RSpec.

    Whenever I have to use anything other than #Ruby, I am immediately reminded of how every single testing framework is miles, no, light-years behind RSpec.

  24. @kerrick And #RSpec.

    Whenever I have to use anything other than #Ruby, I am immediately reminded of how every single testing framework is miles, no, light-years behind RSpec.

  25. @kerrick And #RSpec.

    Whenever I have to use anything other than #Ruby, I am immediately reminded of how every single testing framework is miles, no, light-years behind RSpec.

  26. Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here codeberg.org/codeDude/romodoro
    I having issues trying to mock and stub the dependencies

  27. Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here codeberg.org/codeDude/romodoro
    I having issues trying to mock and stub the dependencies

  28. Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here codeberg.org/codeDude/romodoro
    I having issues trying to mock and stub the dependencies

  29. Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here codeberg.org/codeDude/romodoro
    I having issues trying to mock and stub the dependencies

  30. Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here codeberg.org/codeDude/romodoro
    I having issues trying to mock and stub the dependencies

  31. As expected, the ~65% #RSpec test coverage meant that there have been several issues which came up during manual testing, including some very pleasantly head-scratching ones 🧠

  32. As expected, the ~65% #RSpec test coverage meant that there have been several issues which came up during manual testing, including some very pleasantly head-scratching ones 🧠

  33. As expected, the ~65% #RSpec test coverage meant that there have been several issues which came up during manual testing, including some very pleasantly head-scratching ones 🧠

  34. hspec uses the same syntax Rspec used many years ago.

    Makes me feel nostalgic.

    Had to write a spec for some Ruby code recently, turns out instead of function(args).should_equal result one now has to write expect(function(args).to == result.

    Oh why?

    #haskell #ruby #hspec #rspec

  35. hspec uses the same syntax Rspec used many years ago.

    Makes me feel nostalgic.

    Had to write a spec for some Ruby code recently, turns out instead of function(args).should_equal result one now has to write expect(function(args).to == result.

    Oh why?

    #haskell #ruby #hspec #rspec

  36. hspec uses the same syntax Rspec used many years ago.

    Makes me feel nostalgic.

    Had to write a spec for some Ruby code recently, turns out instead of function(args).should_equal result one now has to write expect(function(args).to == result.

    Oh why?

    #haskell #ruby #hspec #rspec

  37. hspec uses the same syntax Rspec used many years ago.

    Makes me feel nostalgic.

    Had to write a spec for some Ruby code recently, turns out instead of function(args).should_equal result one now has to write expect(function(args).to == result.

    Oh why?

    #haskell #ruby #hspec #rspec

  38. hspec uses the same syntax Rspec used many years ago.

    Makes me feel nostalgic.

    Had to write a spec for some Ruby code recently, turns out instead of function(args).should_equal result one now has to write expect(function(args).to == result.

    Oh why?

    #haskell #ruby #hspec #rspec