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

In-browser end-to-end integration tests #47

Open
divmain opened this issue Aug 29, 2015 · 2 comments
Open

In-browser end-to-end integration tests #47

divmain opened this issue Aug 29, 2015 · 2 comments
Labels

Comments

@divmain
Copy link
Member

divmain commented Aug 29, 2015

Sanity check that changes to build process don't destroy anything when run in supported browsers.

@divmain divmain added this to the v1.0 milestone Aug 29, 2015
@divmain divmain mentioned this issue Aug 29, 2015
61 tasks
@divmain divmain changed the title Two or three in-browser end-to-end integration tests In-browserm end-to-end integration tests Jan 8, 2016
@divmain divmain changed the title In-browserm end-to-end integration tests In-browser end-to-end integration tests Mar 4, 2016
@divmain divmain removed this from the v1.0 milestone Mar 12, 2016
@divmain
Copy link
Member Author

divmain commented Apr 20, 2016

We can test more deeply and thoroughly by relying on jsdom for functional tests. That way, we have direct access to both the build environment and the run-time environment from within a single test. Much of this is already wrapped up into interlock-test-helper.

@divmain
Copy link
Member Author

divmain commented Jun 20, 2016

We're already doing a lot of this in the plugins repo, so porting over the functional test mechanisms from there should suffice to close this issue.

@divmain divmain added the next label Jun 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant