await this.remote
.findById("some-button")
.click()
.end()
.findById("progressbar")
.waitForDeletedById("progressbar");
Find commands will only find elements that are present when the find call hits the browser, or within a short time after (the find timeout). As far as timing goes, the first and second examples are the same. One possibility for catching something like a transient progress bar would be to issue the find for that first, like
await Promise.all([
this.remote.findById('progressbar'),
this.remote.findById('some-button').click()
]);
await this.remote.waitForDeletedById('progressbar');This should work as long as the find and click for the button happen before the find timeout. Even this isn't guaranteed to see the progress bar, though. When a find is issued, the webdriver driving the browser will periodically check for the element until the find timeout expires. If the progress bar appeared and disappeared between two of those checks, it could be missed.
Thanks for the clear description, this helps explain some intermittent failures we've been seeing. I think our best way to avoid any flakiness is to do something like this:
await this.remote
.findById("some-button")
.click()
.sleep(500); // some breathing room to make sure progressbar is added to DOM
await this.remote
.waitForDeletedById('progressbar');I'm not a big fan of sleeps, but probably best we can do, eh?
1 reply
hello. anyone know with intern plugins, how I could/should load a node module to use within the plugin code? I have some plugin code where I am trying to load a JSON file prior to the tests running such like...
// Intern plugin to load t9n json before tests load
var fs = require("fs");
var path = require("path");
intern.registerPlugin("t9nLoader", () => {
var jsonPath = path.join(
__dirname,
"..",
"..",
"src",
"app",
"assets",
"t9n",
"en.json"
);
global.t9n = JSON.parse(fs.readFileSync(jsonPath, "utf-8"));
});and a few other variations....but I can't seem to workout how to get the node modules I need for the plugin. Any help would be appreciated.
("use strict");
intern.registerLoader(function(options) {
var globalObj = typeof window !== "undefined" ? window : global;
options.baseUrl = options.baseUrl || intern.config.basePath;
if (!("async" in options)) {
options.async = true;
}
intern.log("Configuring Dojo loader with:", options);
globalObj.dojoConfig = options;
return intern.loadScript("node_modules/dojo/dojo.js").then(function() {
var require = globalObj.require;
intern.log("Using Dojo loader");
return function(modules) {
var handle;
return new Promise(function(resolve, reject) {
handle = require.on("error", function(error) {
intern.emit("error", error);
reject(new Error("Dojo loader error: " + error.message));
});
intern.log("Loading modules:", modules);
require(modules, function() {
resolve();
});
}).then(
function() {
handle.remove();
},
function(error) {
handle && handle.remove();
throw error;
}
);
};
});
});
//# sourceMappingURL=dojo.js.mapintern.environment) and loaded the appropriate way.
Hi. I'm trying to use intern with a typescript project where I have
{
"compilerOptions": {
"baseUrl": "src",
"paths": {
"@root/*": [ "*" ]
},
...
}
}My editor finds the @root/module imports fine, but when running npx intern the imports can't be found. Is there some configuration in intern.json for that? I couldn't find one.
When running intern, I'd like to override one of the parameters for browser config to come from OS environment. Example, something like
intern config=@sauce-ie11 environments.build=$BUILD_IDIs there some special incantation to merge arguments like that, or is the only choice to supply the entire environments on the command line?
Or alternatively, is there a way to specify that value should be sourced from env in intern.json? Ex
configs: { sauce-ie11: {environments: { build: '$BUILD_ID' ...}}
Hi, I'm having a bit of trouble while trying to automate Safari (14.1.2) on a Mac (BigSur 11.5.2). I'm using Leadfoot 2.3.0 as a standalone binding without Intern. My problem is that when I create a session, I get an error saying
[POST http://localhost:53153/session / {"desiredCapabilities":{"browserName":"safari"}}] Request body does not contain required parameter 'capabilities'.
My code basically does the following:
const capabilities = { browserName: 'safari', fixSessionCapabilities: true };
Server.createSession(capabilities);I took a look at the implementation of Server#createSession() and it seems that it takes the input capabilities and sends them to the REST API as "desiredCapabilities" which would explain why there is no "capabilities" parameter. But if it's a bug, I'm surprised that nobody faced it before...
Am I doing something wrong here?
Arg, would it be an acceptable feature request? And if so, in which timeframe?
On the other hand, what's the value of having Selenium in the stack (apart from the grid features)? Up until now, I've been running all my automation on Windows for Chrome, Firefox and Edge without any problem...
Hey @jason0x43, after running tests on Chrome, FF and Safari, I updated my initial PR on the Leadfoot repo theintern/leadfoot#201. It's not as concise and elegant as the first try because each browser/driver behaves differently (nothing new here... :sob:). Also, the W3C spec differs slightly from the original implementation (W3C WebDriver Spec).
Here are the 2 items on which I request your specific review:
- Capabilities must be filtered to send only capabilities recognized by the remote. I've had to declare the list of W3C official capabilities as an enum in the interfaces. I think it's not the best design and it would be more relevant to filter out all the Leadfoot specific capabilities instead. We could imagine some specific capabilities to an intermediate WebDriver node (such as Selenium server) that would get filtered. Also, I'm not sure about the location of the method
_filterNonW3cCompliantCapabilities. - When receiving "w3c-styled" capabilities, Chrome activates a strict w3c mode which prevents the usage of some endpoints such as /moveto. As a consequence, I added a check on the capability
browserNamebut maybe this could be handled at Session level...?
PS: sorry about the amount of modifications, I forgot to deactivate prettier this time :S
Hello, our intern tests have been running fine and then it stopped working suddenly. It looks like it fails to create sessions. Oddly I can run the tests fine on command line, but it fails running as a scheduled task. Here is the log (and I turned on debug). The tests are on a Windows server. Any pointer would be appreciated. D:\AAInternAutomatedAppTesting\repo>..\node\node.exe .\node_modules\intern\bin\intern.js
[0mDEBUG: Using default loader
DEBUG: Listening for WebSocket connections on port 9001
Listening on localhost:9000 (ws 9001)
Ready[K
Tunnel started
DEBUG: Loaded functional suites: ["tests/intern/functional/COB.js","tests/intern/functional/COBGIS.js"]
DEBUG: Running 1 suites with maxConcurrency null
DEBUG: Queueing suite chrome on any platform
DEBUG: Running suite chrome on any platform
DEBUG: Creating session for {"name":"intern","idle-timeout":60,"browserName":"chrome"}
DEBUG: Suite errored with non-skip error {"name":"TypeError","message":"Cannot read property 'value' of undefined","stack":"TypeError: Cannot read property 'value' of undefined\n at D:\AAInternAutomatedAppTesting\repo\node_modules\@theintern\leadfoot\Server.js:332:26\n at D:\AAInternAutomatedAppTesting\repo\node_modules\@theintern\common\index.js:16:7174\n at processTicksAndRejections (internal/process/task_queues.js:93:5)"}
[1m[33mBUG: suiteEnd was received for invalid session [0m
DEBUG: Emitting functional coverage
[31m(ノಠ益ಠ)ノ彡┻━┻
TypeError: Cannot read property 'value' of undefined
@ node_modules\src\Server.ts:413:19
@ node_modules\@theintern\common\index.js:16:7174
at processTicksAndRejections @ internal\process\task_queues.js:93:5[0m
{
accepted: [ 'redacted@bellevuewa.gov' ],
rejected: [],
envelopeTime: 9,
messageTime: 139,
messageSize: 1052,
response: '250 2.6.0 93dab3e1-9c81-eb2d-221c-14a4fc1966c3@bellevuewa.gov [InternalId=96684008800351, Hostname=BSCEXCLB.ci.bellevue.wa.us] 2500 bytes in 0.126, 19.358 KB/sec Queued mail for delivery',
envelope: { from: 'noreply@bellevuewa.gov', to: [ 'redacted@bellevuewa.gov' ] },
messageId: '93dab3e1-9c81-eb2d-221c-14a4fc1966c3@bellevuewa.gov'
}
Sent email
[1m[31mTOTAL: tested 0 platforms, 0 passed, 0 failed; fatal error occurred[0m
DEBUG: Stopping server...
Stopping[K
DEBUG: Stopped http server
DEBUG: Stopped ws server
Stopped[K