Skip to content
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

Public Methods not public in Verification and Stubbing Proxies #333

Open
AnthonyMillerSF opened this issue Feb 6, 2020 · 2 comments
Open
Labels
good first issue If you're looking to contribute, this issue is the way to go!

Comments

@AnthonyMillerSF
Copy link

I am generating mocks and dropping them in a separate target from my unit tests (so they can be shared among multiple test targets).
The generated functions on __VerificationProxy and __StubbingProxy objects should have the same access modifier as the original function so that I can call them in my unit tests.

My current workaround is to @testable import MyMocksLib but I shouldn't need to use @testable I think.

Thanks :)

@TadeasKriz
Copy link
Member

That's a good catch, probably forgotten in the template.

@TadeasKriz
Copy link
Member

This is a great starter PR for anyone who'd like to contribute.

@TadeasKriz TadeasKriz added good first issue If you're looking to contribute, this issue is the way to go! help wanted This issue is asking for a way to solve a problem. labels Feb 12, 2020
@MatyasKriz MatyasKriz removed the help wanted This issue is asking for a way to solve a problem. label May 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue If you're looking to contribute, this issue is the way to go!
Projects
None yet
Development

No branches or pull requests

3 participants