在 webdriver io 中发现一种奇怪的行为,.equals 方法不起作用,但 ' === ' 在断言中起作用

问题描述 投票:0回答:3

您好,我是 webdriverio 自动化的新手,在练习 webdriverio 时,我发现了一个奇怪的行为。

这是我的测试代码

const internetPage = require("../pages/InternetPage"); //Importing InternetPage in javascript

describe("Handling checkboxes", function(){

it("Check page url ", function(){
    browser.url("/");
    expect(browser.getUrl() === ("https://the-internet.herokuapp.com/"));
});

it("Should click on checkbox", function(){
   // browser.url("/");
    internetPage.clickOnLink(6);

   // browser.pause(1000);
    internetPage.h3Header.waitForDisplayed();
    internetPage.clickOnCheckBox(1);

    expect(internetPage.getCheckboxElement(1).isSelected() === true);

    /**
     * 
     * FYI :  FOUND SOME ISSUE THAT .equal or .equals () method doesnot work instead use === to compare or check whether the actual value is equals to the expected value
     */

    browser.pause(5000);
});

it("check checkbox page header", function(){
    internetPage.clickOnLink(6);
    internetPage.h3Header.waitForDisplayed();
    const text = internetPage.h3Header.getText();
    expect(text === "Checkboxes");
});

});

当我编写这段代码时,我的测试成功通过, 但是如果我使用下面给定的代码

describe("Handling checkboxes", function(){

it("Check page url ", function(){
    browser.url("/");
    expect(browser.getUrl().equals("https://the-internet.herokuapp.com/"));
});

it("Should click on checkbox", function(){
   // browser.url("/");
    internetPage.clickOnLink(6);

   // browser.pause(1000);
    internetPage.h3Header.waitForDisplayed();
    internetPage.clickOnCheckBox(1);

    expect(internetPage.getCheckboxElement(1).isSelected().equals(true));

    /**
     * 
     * FYI :  FOUND SOME ISSUE THAT .equal or .equals () method doesnot work instead use === to compare or check whether the actual value is equals to the expected value
     */

    browser.pause(5000);
});

it("check checkbox page header", function(){
    internetPage.clickOnLink(6);
    internetPage.h3Header.waitForDisplayed();
    const text = internetPage.h3Header.getText();
    expect(text.equals("Checkboxes"));
});

});

然后我的测试功能正常工作,即它启动浏览器,单击复选框并验证该复选框是否已选中,但显示给定的错误。

在此输入图片描述

我的页面对象文件名 InternetPage.js 文件如下

class InternetPage{

get h3Header(){
    return $('h3');
}

getLinkElement(index){
    return $(`ul > li:nth-child(${index}) a`);
}

clickOnLink(index){
    this.getLinkElement(index).waitForDisplayed();
    this.getLinkElement(index).click(); 
}

getCheckboxElement(index){
    return $(`form#checkboxes > input:nth-child(${index})`);
}

clickOnCheckBox(index){
    this.getCheckboxElement(index).waitForDisplayed();
    this.getCheckboxElement(index).click();
}

} module.exports = new InternetPage();

我还附上了我的 package.json 文件

{
    "name": "new_practice",
    "version": "1.0.0",
    "description": "",
    "main": "index.js",
    "scripts": {
        "test": "echo \"Error: no test specified\" && exit 1"
    },
    "keywords": [],
    "author": "",
    "license": "ISC",
    "devDependencies": {
        "@wdio/allure-reporter": "^7.16.13",
        "@wdio/cli": "^7.16.13",
        "@wdio/local-runner": "^7.16.13",
        "@wdio/mocha-framework": "^7.16.13",
        "@wdio/spec-reporter": "^7.16.13",
        "@wdio/sync": "^7.16.13",
        "chai": "^4.3.4",
        "chai-webdriverio": "^1.0.0",
        "chromedriver": "^97.0.0",
        "wdio-chromedriver-service": "^7.2.6"
    }
}

下面是我的 wdio.config.js 文件

exports.config = {
//
// ====================
// Runner Configuration
// ====================
//
//
// ==================
// Specify Test Files
// ==================
// Define which test specs should run. The pattern is relative to the directory
// from which `wdio` was called.
//
// The specs are defined as an array of spec files (optionally using wildcards
// that will be expanded). The test for each spec file will be run in a separate
// worker process. In order to have a group of spec files run in the same worker
// process simply enclose them in an array within the specs array.
//
// If you are calling `wdio` from an NPM script (see https://docs.npmjs.com/cli/run-script),
// then the current working directory is where your `package.json` resides, so `wdio`
// will be called from there.
//
specs: [
    './test/specs/**/*.js'
],
// Patterns to exclude.
exclude: [
    // 'path/to/excluded/files'
],
//
// ============
// Capabilities
// ============
// Define your capabilities here. WebdriverIO can run multiple capabilities at the same
// time. Depending on the number of capabilities, WebdriverIO launches several test
// sessions. Within your capabilities you can overwrite the spec and exclude options in
// order to group specific specs to a specific capability.
//
// First, you can define how many instances should be started at the same time. Let's
// say you have 3 different capabilities (Chrome, Firefox, and Safari) and you have
// set maxInstances to 1; wdio will spawn 3 processes. Therefore, if you have 10 spec
// files and you set maxInstances to 10, all spec files will get tested at the same time
// and 30 processes will get spawned. The property handles how many capabilities
// from the same test should run tests.
//
maxInstances: 10,
//
// If you have trouble getting all important capabilities together, check out the
// Sauce Labs platform configurator - a great tool to configure your capabilities:
// https://saucelabs.com/platform/platform-configurator
//
capabilities: [{

    // maxInstances can get overwritten per capability. So if you have an in-house Selenium
    // grid with only 5 firefox instances available you can make sure that not more than
    // 5 instances get started at a time.
    maxInstances: 5,
    //
    browserName: 'chrome',
    acceptInsecureCerts: true
    // If outputDir is provided WebdriverIO can capture driver session logs
    // it is possible to configure which logTypes to include/exclude.
    // excludeDriverLogs: ['*'], // pass '*' to exclude all driver session logs
    // excludeDriverLogs: ['bugreport', 'server'],
}],
//
// ===================
// Test Configurations
// ===================
// Define all options that are relevant for the WebdriverIO instance here
//
// Level of logging verbosity: trace | debug | info | warn | error | silent
logLevel: 'info',
//
// Set specific log levels per logger
// loggers:
// - webdriver, webdriverio
// - @wdio/browserstack-service, @wdio/devtools-service, @wdio/sauce-service
// - @wdio/mocha-framework, @wdio/jasmine-framework
// - @wdio/local-runner
// - @wdio/sumologic-reporter
// - @wdio/cli, @wdio/config, @wdio/utils
// Level of logging verbosity: trace | debug | info | warn | error | silent
// logLevels: {
//     webdriver: 'info',
//     '@wdio/appium-service': 'info'
// },
//
// If you only want to run your tests until a specific amount of tests have failed 
 use
// bail (default is 0 - don't bail, run all tests).
bail: 0,
//
// Set a base URL in order to shorten url command calls. If your `url` parameter 
 starts
// with `/`, the base url gets prepended, not including the path portion of your 
 baseUrl.
// If your `url` parameter starts without a scheme or `/` (like `some/path`), the 
 base url
// gets prepended directly.
//  baseUrl: 'https://www.amazon.ca/',
baseUrl: 'https://the-internet.herokuapp.com/',
trainerName : "Rutu",
//
// Default timeout for all waitFor* commands.
waitforTimeout: 10000,
//
// Default timeout in milliseconds for request
// if browser driver or grid doesn't send response
connectionRetryTimeout: 120000,
//
// Default request retries count
connectionRetryCount: 3,
//
// Test runner services
// Services take over a specific job you don't want to take care of. They enhance
// your test setup with almost no effort. Unlike plugins, they don't add new
// commands. Instead, they hook themselves up into the test process.
services: ['chromedriver'],

// Framework you want to run your specs with.
// The following are supported: Mocha, Jasmine, and Cucumber
// see also: https://webdriver.io/docs/frameworks
//
// Make sure you have the wdio adapter package for the specific framework installed
// before running any tests.
framework: 'mocha',
//
// The number of times to retry the entire specfile when it fails as a whole
// specFileRetries: 1,
//
// Delay in seconds between the spec file retry attempts
// specFileRetriesDelay: 0,
//
// Whether or not retried specfiles should be retried immediately or deferred to the 
end of the queue
// specFileRetriesDeferred: false,
//
// Test reporter for stdout.
// The only one supported by default is 'dot'
// see also: https://webdriver.io/docs/dot-reporter
reporters: ['spec'],



//
// Options to be passed to Mocha.
// See the full list at http://mochajs.org/
mochaOpts: {
    ui: 'bdd',
    timeout: 60000
},
//
// =====
// Hooks
// =====
// WebdriverIO provides several hooks you can use to interfere with the test process 
 in order to enhance
// it and to build services around it. You can either apply a single function or an 
  array of
// methods to it. If one of them returns with a promise, WebdriverIO will wait until 
 that promise got
// resolved to continue.
/**
 * Gets executed once before all workers get launched.
 * @param {Object} config wdio configuration object
 * @param {Array.<Object>} capabilities list of capabilities details
 */
// onPrepare: function (config, capabilities) {
// },
/**
 * Gets executed before a worker process is spawned and can be used to initialise 
  specific service
 * for that worker as well as modify runtime environments in an async fashion.
 * @param  {String} cid      capability id (e.g 0-0)
 * @param  {[type]} caps     object containing capabilities for session that will be 
  spawn in the worker
 * @param  {[type]} specs    specs to be run in the worker process
 * @param  {[type]} args     object that will be merged with the main configuration 
  once worker is initialised
 * @param  {[type]} execArgv list of string arguments passed to the worker process
 */
// onWorkerStart: function (cid, caps, specs, args, execArgv) {
// },
/**
 * Gets executed just before initialising the webdriver session and test framework. 
  It allows you
 * to manipulate configurations depending on the capability or spec.
 * @param {Object} config wdio configuration object
 * @param {Array.<Object>} capabilities list of capabilities details
 * @param {Array.<String>} specs List of spec file paths that are to be run
 * @param {String} cid worker id (e.g. 0-0)
 */
// beforeSession: function (config, capabilities, specs, cid) {
// },
/**
 * Gets executed before test execution begins. At this point you can access to all 
  global
 * variables like `browser`. It is the perfect place to define custom commands.
 * @param {Array.<Object>} capabilities list of capabilities details
 * @param {Array.<String>} specs        List of spec file paths that are to be run
 * @param {Object}         browser      instance of created browser/device session
 */
// before: function (capabilities, specs) {
// },
/**
 * Runs before a WebdriverIO command gets executed.
 * @param {String} commandName hook command name
 * @param {Array} args arguments that command would receive
 */
// beforeCommand: function (commandName, args) {
// },
/**
 * Hook that gets executed before the suite starts
 * @param {Object} suite suite details
 */
// beforeSuite: function (suite) {
// },
/**
 * Function to be executed before a test (in Mocha/Jasmine) starts.
 */
beforeTest: function () {

    const chai = require('chai');
    const chaiWebdriver = require('chai-webdriverio').default;
    chai.use(chaiWebdriver(browser));

    global.assert = chai.assert;
    global.should = chai.should;
    global.expect = chai.expect;
},
/**
 * Hook that gets executed _before_ a hook within the suite starts (e.g. runs before 
  calling
 * beforeEach in Mocha)
 */
// beforeHook: function (test, context) {
// },
/**
 * Hook that gets executed _after_ a hook within the suite starts (e.g. runs after 
  calling
 * afterEach in Mocha)
 */
// afterHook: function (test, context, { error, result, duration, passed, retries }) {
// },
/**
 * Function to be executed after a test (in Mocha/Jasmine only)
 * @param {Object}  test             test object
 * @param {Object}  context          scope object the test was executed with
 * @param {Error}   result.error     error object in case the test fails, otherwise 
  `undefined`
 * @param {Any}     result.result    return object of test function
 * @param {Number}  result.duration  duration of test
 * @param {Boolean} result.passed    true if test has passed, otherwise false
 * @param {Object}  result.retries   informations to spec related retries, e.g. `{ 
  attempts: 0, limit: 0 }`
 */
// afterTest: function(test, context, { error, result, duration, passed, retries }) {
// },


/**
 * Hook that gets executed after the suite has ended
 * @param {Object} suite suite details
 */
// afterSuite: function (suite) {
// },
/**
 * Runs after a WebdriverIO command gets executed
 * @param {String} commandName hook command name
 * @param {Array} args arguments that command would receive
 * @param {Number} result 0 - command success, 1 - command error
 * @param {Object} error error object if any
 */
// afterCommand: function (commandName, args, result, error) {
// },
/**
 * Gets executed after all tests are done. You still have access to all global 
  variables from
 * the test.
 * @param {Number} result 0 - test pass, 1 - test fail
 * @param {Array.<Object>} capabilities list of capabilities details
 * @param {Array.<String>} specs List of spec file paths that ran
 */
// after: function (result, capabilities, specs) {
// },
/**
 * Gets executed right after terminating the webdriver session.
 * @param {Object} config wdio configuration object
 * @param {Array.<Object>} capabilities list of capabilities details
 * @param {Array.<String>} specs List of spec file paths that ran
 */
// afterSession: function (config, capabilities, specs) {
// },
/**
 * Gets executed after all workers got shut down and the process is about to exit. An 
  error
 * thrown in the onComplete hook will result in the test run failing.
 * @param {Object} exitCode 0 - success, 1 - fail
 * @param {Object} config wdio configuration object
 * @param {Array.<Object>} capabilities list of capabilities details
 * @param {<Object>} results object containing test results
 */
// onComplete: function(exitCode, config, capabilities, results) {
// },
/**
* Gets executed when a refresh happens.
* @param {String} oldSessionId session ID of the old session
* @param {String} newSessionId session ID of the new session
*/
//onReload: function(oldSessionId, newSessionId) {
//}
}
javascript automation automated-tests selenium-chromedriver webdriver-io
3个回答
0
投票

欢迎来到 Stackoverflow!

恐怕您使用的断言格式与库文档不符。从文档here来看,似乎没有简单的方法来断言当前的 URL。也许你可以检查 webdriverio 本身提供的断言库,并且可以在here找到文档。


0
投票

尝试下面的代码,你可以看到结果-

等待期望(文本).toHaveText(“复选框”)


0
投票

我看到您包含了

wdio/sync
包,所以这个答案可能不正确。但是,当忘记等待异步函数的结果时,我看到了图像中出现的错误。这意味着您实际上是在 Promise 对象上调用
equals
方法,而不是函数的结果 - 因为 Promise 尚未解析为返回值。

Webdriverio 退休了他们的“同步”选项,但我看到该包包装了所有内容以使其再次同步。也许它并不能 100% 完成工作。

在(正常)异步操作中,您需要等待异步函数的结果,例如

.getUrl
,因此一般条件需要是:

(await browser.getUrl()) === "https://the-internet.herokuapp.com/"

expect
为您处理异步,因此使用起来可能更清晰

await expect(browser).toHaveUrl("https://the-internet.herokuapp.com/")

或者寻找片段,例如

await expect(browser).toHaveUrl(expect.stringContaining('the-internet.herokuapp.com'))
© www.soinside.com 2019 - 2024. All rights reserved.