senocular

javascript: document.title = prompt("Rename Tab"); return false;

senocular

function BitmapData(canvas){
	this.canvas = canvas;
	this.width = this.canvas.width;
	this.height = this.canvas.height;
	this.context = this.canvas.getContext("2d"); 
	this.imageData = null;
	
	// true if the canvas has been drawn into 
	// and the image data has not been updated
	this.dataInvalid = false;

senocular

console.log('github', document.readyState)
document.addEventListener('DOMContentLoaded', function(){
  console.log('github ready')
})

senocular

class FunctionSequencer {

    constructor (genFunc) {

        if (Object.prototype.toString.call(genFunc) !== '[object GeneratorFunction]') {
            throw new TypeError('Failed to create FunctionSequencer instance: parameter 1 is not of type \'GeneratorFunction\'.');
        }

        this._genFunc = genFunc;
        this._codeBlocks = this._parseBlocks(this._genFunc);

senocular

alert('hi');

senocular

Hooks before/beforeEach continues to running test(s) before their command queue is finished.

When running commands without an async done callback in a before and/or beforeEach, the next test is run before the command queue within the before/beforeEach is complete.

module.exports = {
    beforeEach: function (browser) { // or before
        browser.pause(1000, function() {
            console.log('beforeEach pause complete')
 })

senocular

• all callbacks use result object
• custom commands, page object/section commands have same behavior/interface
• client/api property consistency
• better separation of user-defined apis and internal properties (page objects etc)
• page/section objects have full api surface
• Page objects, commands classes, having proper instanceof-checkable instances (no weird F() constructor)
• Support command overrides rather than throwing an error
• no legacy stuff
  • afterEach hook can receive the browser object only in its async form
• async behavior consistency/clarity

senocular

[DEPRECATED - PLEASE USE THE NIGHTWATCH WIKI VERSION MOVING FORWARD]

https://github.com/nightwatchjs/nightwatch/wiki/Understanding-the-Command-Queue

Understanding the Command Queue

When Nightwatch runs a test, it processes its commands in a list known as the command queue. This list manages the asynchronous execution of the commands defined in that test.

As a queue, the command queue generally follows the rule of first in, first out (FIFO). The first command you call in a test is the first executed when the test runs. The second command is called next, followed by the next command up until the last command added, which becomes the last command executed.