You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an issue, but a question. I am debating whether or not to have a spec for my organizers. This spec works to enforce that the order of the interactors in my organizer doesn't change, but I think it might not be a good idea to include organizer.organized in my own project specs because it's not really part of the public API. Any thoughts on this?
describeDibs::SetupWizard::SetupUserAccountdosubject(:organizer){described_class}it"organizes flow of interactors to setup a user account"doexpect(organizer.organized).toeq([Dibs::SetupWizard::BuildEmployee,Dibs::SetupWizard::SaveEmployee,Dibs::SetupWizard::CreateUserPassword])endend
The text was updated successfully, but these errors were encountered:
I've got an ActiveSupport::TestCase version of this:
defassert_organizes(organizer,interactors)assert_equalinteractors,organizer.organized,"Expected #{organizer} to organize #{interactors.to_sentence} but didn't"end
And used like so:
require'test_helper'classSubscriptionChangeTest < ActiveSupport::TestCasetest"is an organizer"doassert_organizesSubscriptionChange,[HiringRoleManager,NewHirerTasks,FeatureDowngrade]endend
This is probably my favorite gem - thank you!
Not an issue, but a question. I am debating whether or not to have a spec for my organizers. This spec works to enforce that the order of the interactors in my organizer doesn't change, but I think it might not be a good idea to include
organizer.organized
in my own project specs because it's not really part of the public API. Any thoughts on this?The text was updated successfully, but these errors were encountered: