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?

#rails #coding #programming #unitTest #softwareDevelopment

@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.

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

shoulda-matchers가 실제로 당신을 위해 하는 일

shoulda-matchers는 Rails 테스트 코드를 간결하고 가독성 높게 만들어주며, 모델의 계약을 명확히 문서화합니다.

#rspec #rails_testing
https://ruby-news.kr/articles/what-shoulda-matchers-is-actually-doing-for-you

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 🧠

RSpec `have_attributes` 내 복잡한 문자열 검증: `satisfy` 매처 활용

RSpec `have_attributes` 매처 사용 시, 문자열 속성에 대한 복합적인 포함/미포함 조건 검증의 한계점을 제시합니다.

#rspec
https://ruby-news.kr/articles/rspec-satisfy-matcher

SecureRandom を stub すると、なぜ Rails の CSRF が壊れるのか
https://qiita.com/okarina-chaan/items/747be079183dd0d6cc83?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Rails #RSpec #stub

도쿄 가스의 재난 방지 최전선을 지키는 Ruby: 지진 대응 시스템 SUPREME 사례

도쿄 가스는 Ruby 기반의 SUPREME 시스템을 통해 지진 발생 시 가스 공급을 자동 제어하며 대규모 화재와 폭발로부터 시민들을 보호하고 있습니다.

#rspec
https://ruby-news.kr/articles/ruby-at-the-front-line-of-disaster-prevention

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

Nice article about structuring your tests #ruby #rspec https://thoughtbot.com/blog/the-arrange-act-assert-pattern

🥳 Happy 30th birthday to #RubyLang, still my favorite programming language! Here's a coupon for my #RSpec book for just $9, with practice #TDD advice. Free updates for Rails 8.1 and Ruby 4 coming early next year! Boosts appreciated! 🥳

https://leanpub.com/everydayrailsrspec/c/ruby30

#mildlysatisfying #rspec4Life #rspec
10591 is the zip code for Tarrytown, NY, the real world setting of Washington Irving's "The Legend of Sleepy Hollow".

This. I've seen a lot of garbage tests this year. I like #RSpec's `xit` shorthand for walking more slowly and deliberately through test scenarios, regardless of whether an agent is involved or not.

https://www.andy-gallagher.com/blog/stop-vibe-coding-your-unit-tests/

TIL in #Ruby #RSpec,

this:

expect(File.exist?(old_file)).to be true

can be shortened to this:

expect(File).to exist(old_file)

expect(File).to exist old_file

Neat!

@postmodern and also, why doesn't #Ruby itself have an opposite direction of .include? method?

[1, 2, 3].include? 1

Like #Rails’ .in?

1.in? [1, 2, 3]

Then the #RSpec would be:

expect(1).to be_in [1, 2, 3]

continuing about collection-based #rspec matchers...

When using `match` and `include` you can let the `it` spec to speak for itself:

```ruby
context 'when one of the values is off' do
it do
expect(subject).to match(
error: 'P',
context: be_a(String).and( eq('S'))
)
end
end
```

I tend to not declare what the `it` is, because it's gratifying see its errors :), usually that's the context blocks are for.

* puns intended
# ruby

@benjamineskola I'd argue that relying on concrete type is something the spec shouldn't care, at least not in #ruby

For example, perhaps it started with a hash, and that was OK, but later on the team want to change the implementation to use something else, like a Struct class.

Error = Struct.new('ErrorStruct', :error, :context)

error = Error.new('Pusher error', 'oops!')

then `be_hash_including` might fail because it's not a hash, is an Struct. Image having 433 spec files :(

#rspec

Lately I've found some resistance to use collection-based #rspec matchers

Checking element by element is technically not wrong:

expect(failure[:error]).to eq('Pusher error')
expect(failure[:context]).to eq('notify_notification_started')

but using `match` & `include` has their advantages:

expect(failure).to match(
error: 'Pusher error'
context: 'notify_notification_started'
)

I can elaborate further if someone ask for it.

Perhaps a blog post about it is needed?

#ruby

## Please Don't Nerf RubyLang Because #StyleGuides

Ruby has made some internal changes that remind me of the changes #RSpec made to clean up internals but uglified the code & made certain features simply stop working as expected.

Removing `foo rescue nil` is an exmaple. Some edge cases make this antipattern useful; replacing a one-liner with a complex method/chain is annoying. Mindful chainsaw-juggling gave expert #Rubyists superpowers. Not trusting power users is red #Kryptonite for code.

One downside of setting myself the stretch goal of "adding #RSPec tests for all URL routes" is that there are a LOT of them 😅

(`rails routes` says 303)

This is of course making this task take forever (~15 hours' work to improve test coverage from ~40% to ~65%).

But, more also-importantly, it's ruining my "lines of code deleted" metric, I have added over 2000 lines of specs alone 🙈