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

Testing #11

Open
stonelasley opened this issue Aug 2, 2017 · 2 comments
Open

Testing #11

stonelasley opened this issue Aug 2, 2017 · 2 comments
Milestone

Comments

@stonelasley
Copy link
Owner

stonelasley commented Aug 2, 2017

Not completely sure how this would work. Instantiate a spy and check the member exists and returns the right type, should be simple enough. Would be nice to reference Ionic type and iterate over members to check if exists.

@stonelasley stonelasley changed the title Actual tests Testing Aug 18, 2017
@stonelasley
Copy link
Owner Author

stonelasley commented Aug 18, 2017

I want to keep this open as the nature of this project, essentially (shallowly) mirroring a much larger project, presents some challenges and the current method of testing may be more work than it's really worth. https://github.com/stonelasley/ionic-mocks/blob/master/src/angular/platform.spec.ts

@Remco75
Copy link

Remco75 commented Oct 11, 2017

Just a wild thought: It would be nice to be able to fetch the ionic-type during build-time. Then iterate over it to find implementation that are mocked, not mocked, or that are mocked and no longer exist. That way you could even make a progress report as to how far the mock-implementation is.

Maybe even generate default mocks based on the type for implementations that do not yet exist. (interesting stuff) :-)

@stonelasley stonelasley added this to the Version 3 milestone Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants