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

run browser tests on ci #5

Closed
wants to merge 10 commits into from
Closed

Conversation

wenzowski
Copy link
Contributor

This depends on #4 so merge that first.

The encrypted env var will start working as soon as this is merged, though travis will have to be enabled for the repo of course.

Backchannel 2014-2-28

9:39:35 PM nateps: doing cross browser testing should be a priority now that things are getting more stable in derby
9:40:21 PM nateps: you can probably write the tests in a way where they can be run in phantom or loaded as a normal html page

Took longer than I'd hoped to get this figured out, but here it is.

moar staktracse

@wenzowski
Copy link
Contributor Author

here's what it would look like https://travis-ci.org/wenzowski/saddle/builds/20442342

formatting suggestions welcome

@wenzowski
Copy link
Contributor Author

concurrent builds on travis currently clobber each other travis-ci/travis-ci#1366

open sauce allows 3 concurrent builds
@pypmannetjies pypmannetjies added the stale Older or abandoned issues we will not fix label Nov 19, 2020
@ericyhwang
Copy link
Contributor

We're now going to move the DOM-based tests to be runnable with JSDOM, and use GitHub Actions for CI, since Travis has had large open-source backlogs the past month:
#34

@ericyhwang ericyhwang closed this Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Older or abandoned issues we will not fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants