Login
55
Day:
Sunday
Time:
1:30p
Room:
Doheny Beach A
Small, unexpected front-end changes are tough to spot manually and can be a signal for larger problems. And feature requests, bug fixes may lead to performance issues that actually stem from the Frontend. Rapid development cycles, large page counts and developer fatigue can make it difficult to catch even obvious mistakes before they go live.
We will talk about why testing your frontend matters, tools you can use for frontend testing (both Visual Regression Testing and Performance Testing) and how to tie it all together into your workflow.
Category:
DevOps
Skill:
Intermediate
Duration:
One hour
- Log in to post comments
Comments
Peter Kosenko replied on Permalink
Acronyms
I suppose if people don't know what "CI" is, they may not belong in this session, BUT I am also an editor who was trained to remind writers that they should spell out any acronyms at least once. So: "Continuous Integration." At least in the title of the talk.
https://en.wikipedia.org/wiki/Continuous_integration
btmash replied on Permalink
Changed to 'Automated Testing'
Continuous Integration might be confusing as well. Changed to automated testing.
Emb03 replied on Permalink
Picking this session
Picked
btmash replied on Permalink
Thank you for attending
I hope those of you that made it out to the session got something out of it and think about what you can do to ease frontend issues. The slides are up at http://btmash.github.io/reveal-frontend along with links to the codebase for the slides and examples.
frob replied on Permalink
Link to the video:http:/
Link to the video:
http://replay.uci.edu/clients/drupal/DrupalCamp-Automated_Testing_for_th...