-
Notifications
You must be signed in to change notification settings - Fork 8
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 #2
Comments
@twolfson I seem to have lost admin writes to this repo during the transfer process so I can't set up travis intergration? Could you configure it please because you appear to be the owner now 😄 |
Ah, looks like you made a team. Nice =) It looks like we might need 2 teams though, 1 for maintainers and 1 for owners of repos. Going to do that |
Alright, done and done. You should be good to go now. |
Travis building now 👍 |
To answer the question "How do we test a theming library?", there is an area of testing known as Visual regression/Perceptual diff testing. I wrote an article a while back which should be enlightening:
http://twolfson.com/2014-02-25-visual-regression-testing-in-travis-ci
The tl;dr of it is, log into application, navigate pages, take screenshots, compare screenshots to expected screenshots. Since the time of writing there have been some more testing libraries created, e.g. gemini, which is what I use at work (although with a mod for full page screenshots):
https://github.com/bem/gemini
We should be able to reuse the BrowserStack harness from
gmusic.js
to handle all the authentication and navigation.For the interim, we should still have CI set up that only runs linting (so there's some test infrastructure).
The text was updated successfully, but these errors were encountered: