#rspec — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #rspec, aggregated by home.social.
-
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 🤗
-
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 🤗
-
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 🤗
-
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 🤗
-
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 🤗
-
【Rails】RSpecの導入からモデルテストを書き方まで|FactoryBot・Fakerでハマったポイントまとめ
https://qiita.com/masa_tech_0326/items/b5f51a60674113a91158?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
【Rails】RSpecの導入からモデルテストを書き方まで|FactoryBot・Fakerでハマったポイントまとめ
https://qiita.com/masa_tech_0326/items/b5f51a60674113a91158?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
This is an interesting article about parallel testing and CI https://visuality.pl/posts/parallel_tests_without_waiting
-
This is an interesting article about parallel testing and CI https://visuality.pl/posts/parallel_tests_without_waiting
-
This is an interesting article about parallel testing and CI https://visuality.pl/posts/parallel_tests_without_waiting
-
This is an interesting article about parallel testing and CI https://visuality.pl/posts/parallel_tests_without_waiting
-
This is an interesting article about parallel testing and CI https://visuality.pl/posts/parallel_tests_without_waiting
-
⚡ 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 🇯🇵
-
⚡ 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 🇯🇵
-
⚡ 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 🇯🇵
-
⚡ 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 🇯🇵
-
⚡ 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 🇯🇵
-
Hi #ruby community I'm looking for other recommendation here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/countdown.rb
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?
-
Hi #ruby community I'm looking for other recommendation here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/countdown.rb
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?
-
Hi #ruby community I'm looking for other recommendation here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/countdown.rb
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?
-
Hi #ruby community I'm looking for other recommendation here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/countdown.rb
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?
-
Hi #ruby community I'm looking for other recommendation here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/countdown.rb
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?
-
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.
-
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.
-
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.
-
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.
-
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.
-
Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/command_server.rb#L24
I having issues trying to mock and stub the dependencies -
Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/command_server.rb#L24
I having issues trying to mock and stub the dependencies -
Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/command_server.rb#L24
I having issues trying to mock and stub the dependencies -
Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/command_server.rb#L24
I having issues trying to mock and stub the dependencies -
Hello #ruby people, How can I test using #Rspec that accept method is receive(triggered). The class is here https://codeberg.org/codeDude/romodoro-socket/src/branch/main/lib/romodoro/socket/timer/command_server.rb#L24
I having issues trying to mock and stub the dependencies -
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 🧠
-
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 🧠
-
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 🧠
-
SecureRandom を stub すると、なぜ Rails の CSRF が壊れるのか
https://qiita.com/okarina-chaan/items/747be079183dd0d6cc83?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
SecureRandom を stub すると、なぜ Rails の CSRF が壊れるのか
https://qiita.com/okarina-chaan/items/747be079183dd0d6cc83?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items -
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?
-
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?
-
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?
-
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?
-
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?
-
Nice article about structuring your tests #ruby #rspec https://thoughtbot.com/blog/the-arrange-act-assert-pattern
-
Nice article about structuring your tests #ruby #rspec https://thoughtbot.com/blog/the-arrange-act-assert-pattern
-
Nice article about structuring your tests #ruby #rspec https://thoughtbot.com/blog/the-arrange-act-assert-pattern