After I got my sample working with the help of A hanami slice in a Rails app - #8 by cllns I ran into a testing issue, which makes me wonder whether I even understood the basic of how you’d use / test the result of an operation: rm -rf hanami_sample2 hanami new hanami_sample2 cd hanami_sample2 mk…

I haven’t had a ton of time to look into it, but I’m stumped why config.include Dry::Monads[:result] in the operations spec support file isn’t working. Even directly including include Dry::Monads[:result] directly in the spec isn’t working :thinking: As for the other issue, you need to put step in …

Thank you, @cllns ! This allows me to fully implement my bigger example… ah, not quite. I will, once again switch to a new topic, Rails and hanami-view don't get along , to discuss a different issue.

[image] cllns: I haven’t had a ton of time to look into it, but I’m stumped why config.include Dry::Monads[:result] in the operations spec support file isn’t working. Even directly including include Dry::Monads[:result] directly in the spec isn’t working :thinking: Ah so this is as simple as …

I’ve been dealing with this annoyance for a long time. Here’s the thing: it does give you access to those class constants, but RSpec is a special case because everything is written in blocks, and so the scope of constant lookup is actually the global scope, and not the ExampleGroup class. I’m not c…

Ahhh yes, I see. That makes sense @alassek , thanks for the insight. Wouldn’t this work as well as our operation spec support file, to get the short-hand Success and Failure constants only for specs? So we don’t pollute the global namespace. # frozen_string_literal: true require "dry/monads" RSpe…

Here’s a reason why I don’t like adding these to the global scope: if you are referencing one of them in a place where normally those constants wouldn’t exist, you won’t see this bug in your test suite, only in production. I think if you’re going to do this, it needs to go all the way. You need to …

Ah of course. I was thinking it would just define it within RSpec’s context, but it does pollute the global namespace for app code too, and I agree that’s a bad idea. I once got bit by something similar (using FactoryBot, which was adding a monkey patch only in test, but not production). @flash-gor…

I added an extension to rspec in main dry-monads/CHANGELOG.md at e4339f8b44cf2405305e4b7a5a92c10cdce3b7e1 · dry-rb/dry-monads · GitHub Works for me so far! Needless to say I’m happy since it simplifies a lot of code, thanks for the nudge!

Works for me, after adding Dry::Monads.load_extensions(:rspec) to spec/support/operations.rb I added a comment to the issue about an idea for a different way we could possibly implement this.

Trouble testing the result of an operation

questions

alassek February 17, 2025, 5:58pm 9

That const_missing trick is interesting. I’ll have to experiment with it.

Rails app with hanami fails on hanami dependency I didn't (want to) add

Topic		Replies	Views
Standalone testing of actions in rc1 issues	5	509	November 15, 2022
Feedback on Hanami Minitest development	9	196	March 27, 2026
A hanami slice in a Rails app questions	8	212	February 15, 2025
rspec causes issues when using action generator issues	7	100	January 22, 2026
What is hanami? Where is it going? questions	7	7341	April 26, 2016

Trouble testing the result of an operation

Related topics