-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop including full Aruba API in Cucumber World or RSpec spec class #694
Milestone
Comments
I think this would be something that would definitely prove tricky, but would provide good value, because then it starts to remove itself from the whole monkeypatch philosophy into a more OO one. I might be able to dig into this a bit if you'd like, alongside other stuff. |
Hi @luke-hill it would be great if you can take a look at this. There's no rush since this is for the 2.0 release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Aruba exposes a large set of API methods into the test environment. It would be cleaner to access these through a dedicated object.
Expected Behavior
Something like:
Current Behavior
Possible Solution
This needs to be changed in several steps:
Context & Motivation
Aruba's API is massive and testing it clearly is difficult because the methods are exposed to Aruba's specs as well. Also, exposing these through a real object makes it clearer for end users to see where the methods they call come from.
The text was updated successfully, but these errors were encountered: