andrewdavey / witness Goto Github PK

Very handily witness stashes the settings selected on the setup screen in a cookie, the cookie is a session cookie though and is lost between browser sessions, would it be possible to make this a persistant cookie with a reasonable expiry ?

Is the reload button supposed to reload the spec files ( ie pick up changes made to the tests without going back to the 'setup' screen ) ? If so .. it doesn't seem to reload / pick up changes to the tests ...

Clicking Run All by mistake can be annoying, especially if, for example, the web server under test is not running yet.
Add a stop button to the UI.

This may require surgery to the underlying action runner to add cancellation support.

Verify if this is broken or not.

{
    when: -> @result = $(".foo").attr("href")
}

Rather than reloading the entire runner, just reload the selected specification file or directory.

Will need a UI overlay to display download and parse log and errors.

Add inclusive and exclusive boundary support.

should.beBetween 100, "exclusive", 200, "inclusive"
should.beBetween 100, 200, "inclusive"

?

Other than hacking the global default timeout for AsyncAction, there should be a way to set the timeout of any async action instance.

Perhaps a modifier function:

when: loadPage("/").withTimeout(5000)

dsl.extendShould({

beVisible: {
    getActual: function (propertyNames) {
        return jQuery(propertyNames[0], this.document);
    },
    test: function (actual) {
        return actual.is(":visible");
    },
    description: function (selector) {
        return selector + " should be visible";
    },
    error: function (selector, actual) {
        return selector + " is not visible";
    }
}

});

If in a "then" assertion you test different conditions on the same selector, e.g.:

"#myDiv span": should.haveText "This text"
"#myDiv span": should.match 1

only the second assertion is picked up by witness.