| /*global browser:false*/ | |
| var selenium = require("selenium-standalone"); | |
| var Promise = require("bluebird"); | |
| exports.config = { | |
| // Other configs go here | |
| // | |
| // ===== | |
| // Hooks |
Images are stored in the Git repo like any other file. This makes is simple to share baseline images across the teams. It also allows for changes in the baseline to be tracked over time.
Whether or not updates to the baseline images are accepted depends on the goal of the changes. Here are a few scenarios:
| https://www.npmjs.com/package/es6-template-strings | |
| userCity:{name: "UserCity", selector:"//input[@ng-model='${selector1}']/${selector2}", isTextEntry:true}, | |
| browser.addCommand(commandPrePend + "_" + commandEntry.name + "_setValue" , function(textValue, selectors) { | |
| var selector = templatE(commandEntry.selector, selectors); |
| var expect = require("chai").expect; | |
| var _ = require("lodash"); | |
| var checkMismatch = function(err, res) { | |
| expect(err).to.not.exist; | |
| _.forOwn(res, function(elementShots) { | |
| elementShots.forEach(function(shot) { | |
| expect(shot.isWithinMisMatchTolerance).to.equal(true, "'" + shot.properties.name + "' visual " + shot.message); | |
| }); |
| [{ | |
| "browser": "ie", | |
| "browser_version": ["11.0", "10.0"], | |
| "os_version": ["10", "8.1"] | |
| }] |
| // @see https://github.com/webdriverio/webdrivercss/issues/103 | |
| var assert = require("assert"); | |
| function assertShots (err, shots) { | |
| assert.ifError(err); | |
| Object.keys(shots).forEach(function(element) { | |
| shots[element].forEach(function(shot) { | |
| assert.ok(shot.isWithinMisMatchTolerance, shot.message); | |
| }) |
| /** | |
| * Resets the browser for the next set of tests and sets the test name | |
| * for Browserstack organization | |
| * | |
| * @param {object} mochaTest The Mocha 'test' object (should be `this` in your tests) | |
| * @param {object} [viewportSize] | |
| * @param {number} [viewportSize.width] - Viewport width; defaults to 1280 | |
| * @param {number} [viewportSize.height] - Viewport height, defaults to 960 | |
| * @example | |
| * browser.startNewSession(this); |
| var chai = require('chai'); | |
| var expect = chai.expect; | |
| describe('Landing Page', function() { | |
| beforeEach(function () { | |
| browser.url('http://webdriver.io.s3-website-eu-west-1.amazonaws.com/'); | |
| }); | |
| it.only('should have the right title', function () { | |
| var title = browser.getTitle(); |
| module.exports = { | |
| // | |
| // Framework to run your tests with. | |
| framework: "mocha", | |
| // | |
| // Options to be passed to Mocha. | |
| // See the full list at http://mochajs.org/ | |
| mochaOpts: { | |
| ui: "bdd", | |
| timeout: 270000, |
Testing can be a real pain! Isn't it good enough that it looks fine in Chrome? Should I really have to test the login page for a change to the contact form?
As a front-end dev, I've lazily assumed that testing is the realm of QA. Sure, I'll begrudgingly check my site in IE to see how much repair it needs, but I confess to cutting corners when testing and saying "That shouldn't break anything..."
This worked okay while I was building small sites, but now that I'm working with multiple teams on large projects, cutting corners doesn't work. The edge case always comes in to play and things that probably won't break do.