At the moment, the only way to view a script is by code. It would be nice to have an option to see the script represented visually, similarly to Studio, where each action is presented as a label.

Right now scripts are written as plain function-less javascript. This means every script has to start with an instantiation of Agent, since everything is done through webdriver agents. It might make more sense to require scripts to define a function that takes an agent as a parameter. This could also serve as a hook for test variables, as per #9

Latest version (39) works on some pages and not others. When tests fail, the agent reports an error stating that it did not have permission to access a property named "uuid". This occurs when it gets the html element (which it does by default, even if the script only navigates to a page then quits).

I.e. call a script from inside another script

CSS loads differently the first time the control-room is opened (or if caching is turned off)

Currently, there is no way to run multiple scripts. The agent has a method that allows javascript code to be executed on the page, but we can't run another script by name. Which makes sense, since agents themselves don't have access to other scripts.

This could be accomplished by adding a parse step before handing over the code to the virtual machine. The simplest way would be to parse the script for certain directives and replace those directives with corresponding tests, i.e.:

If test1.js is defined as
{
var agent = new Agent();
agent.gotoUrl("localhost:8083/thing1");
assertEqual(agent.getSource(), "someBody");
}

and test2.js is defined as
{

runTest("test1.js");

var agent = new Agent();
agent.gotoUrl("localhost:8083/thing2");
assertContains(agent.getSource(), "span");
}

then the actual code sent to the virtual machine when running test2.js would be:
{
var agent = new Agent();
agent.gotoUrl("localhost:8083/thing1");
assertEqual(agent.getSource(), "someBody");

var agent = new Agent();
agent.gotoUrl("localhost:8083/thing2");
assertContains(agent.getSource(), "span");
}

We should have a way to set testing variables, e.g. marking login information as a variable, and consequently being able to quickly modify the variable and run the test again. Or better yet, we could set up a script that runs a test multiple times with different variables, e.g.:

var agent = new Agent();

agent.runTest({"username": "montage"});
agent.runTest({"username": "declarativ"});

etc..

Currently, something like this is possible inside individual scripts by wrapping the whole test in a function and extracting literals into variables, but this requires manual work and it would be better if it was more automated

Somewhere in the vicinity of 1.4 trillion seconds

Had to modify a file in the serve-index in order for HTTP to work correctly in screening. As a result I had to include the entire express module as part of the screening source. Once express is upgraded to 4.x (breaking change) we can have a separate branch instead of a copy of the source.

E.g., remove the chrome agent and add a firefox agent. Refresh the server and the firefox will appear to still be there, even though it has actually been replaced by the chrome driver.

E.g. the script variables dialog or the batch step config dialog

Doesn't seem to break anything but it's worth investigating