Download to read offline
![@trentmwillis #dotjs
QUnit.test.inBrowser(title, {
url,
injections: ['node_modules/axe-core/axe.min.js']
}, async function(assert) {
const content = document.getElementById('content');
const results = await axe.run(content);
assert.equal(results.violations.length, 0);
});](https://image.slidesharecdn.com/dot-jsworking-well-future-testing-171207174716/75/Working-Well-The-Future-of-Web-Testing-19-2048.jpg)
![@trentmwillis #dotjs
const pages = [ /* pages in site */ ];
pages.forEach(page => {
QUnit.test.inBrowser(`${title} - ${page}`, {
url: page,
injections: ['node_modules/axe-core/axe.min.js']
}, async function(assert) {
const content = document.getElementById('content');
const results = await axe.run(content);
assert.equal(results.violations.length, 0);
});
});](https://image.slidesharecdn.com/dot-jsworking-well-future-testing-171207174716/75/Working-Well-The-Future-of-Web-Testing-20-2048.jpg)
More Related Content
Similar to Working Well: The Future of Web Testing
Working Well: The Future of Web Testing
- 2. @trentmwillis #dotjs Working Well: TheFuture of Web Testing |Trent Willis @trentmwillis QUnit Project Lead
- 3. @trentmwillis #dotjs Testing GivesUs Confidence That Software Works
- 4. @trentmwillis #dotjs Testing ShouldGive Us Confidence That Software Works Well
- 5.
- 6.
- 7.
- 8.
- 9.
- 10. @trentmwillis #dotjs chrome --headless + ChromeDevTools Protocol = New Possibilities
- 11.
- 12. @trentmwillis #dotjs const browser= await puppeteer.launch(); const page = await browser.newPage(); await page.goto('https://example.com'); await page.content(); await page.screenshot({ path: 'screenshot.png' }); await browser.close();
- 13.
- 14. @trentmwillis #dotjs const title= 'Home page successfully renders'; const url = 'https://localhost:8000/'; QUnit.test.inBrowser(title, url, function(assert) { const content = document.getElementById('content'); assert.ok(content, 'main content is rendered!'); });
- 15. @trentmwillis #dotjs How isthis the future?
- 16. @trentmwillis #dotjs How isthis the future? Less about “how” More about “what”
- 17.
- 18.
- 19. @trentmwillis #dotjs QUnit.test.inBrowser(title, { url, injections:['node_modules/axe-core/axe.min.js'] }, async function(assert) { const content = document.getElementById('content'); const results = await axe.run(content); assert.equal(results.violations.length, 0); });
- 20. @trentmwillis #dotjs const pages= [ /* pages in site */ ]; pages.forEach(page => { QUnit.test.inBrowser(`${title} - ${page}`, { url: page, injections: ['node_modules/axe-core/axe.min.js'] }, async function(assert) { const content = document.getElementById('content'); const results = await axe.run(content); assert.equal(results.violations.length, 0); }); });
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28. @trentmwillis #dotjs await Profiler.startPreciseCoverage(); //Trigger some action const { result } = await Profiler.takePreciseCoverage(); // Assert against results or track over time
- 29.
- 30.
- 31. @trentmwillis #dotjs The FutureIs Accessible
- 32. @trentmwillis #dotjs The FutureIs Performant
- 33. @trentmwillis #dotjs The FutureIs Necessary
- 34. @trentmwillis #dotjs The FutureIs Bright |Trent Willis @trentmwillis QUnit Project Lead