gulp-protractor

gulp-protractor error with chrome v54 / web driver v2.25

◇◆丶佛笑我妖孽 — Thu, 16 Jan 2020 21:22:20 +0000

gulp-protractor error with chrome v54 / web driver v2.25 ◇◆丶佛笑我妖孽 2020-01-17 05:22:20

问题

Due to the latest update of chrome (v54) we've noticed our protractor tests failing. We attempted to update to the latest version of gulp-protractor (v3.0.0) which in turn downloads the latest web driver (v2.25) to resolve the issue but unfortunately a new error occurs we've been unable to resolve.

Everything worked fine before chrome's update.

Our protractor configuration is as follows:

exports.config = {
  // Capabilities to be passed to the webdriver instance.
  capabilities: {
    'browserName': 'chrome'
  },

  onPrepare: function () {
      var fs = require('fs');
      var testDir = 'testresults/';
      if (!fs.existsSync(testDir)) {
          fs.mkdirSync(testDir);
      }

      var jasmineReporters = require('jasmine-reporters');

      // returning the promise makes protractor wait for the reporter config before executing tests
      return browser.getProcessedConfig().then(function () {
          // you could use other properties here if you want, such as platform and version

          var browserName = 'browser';
          browser.getCapabilities().then(function (caps) {
              browserName = caps.caps_.browserName.replace(/ /g, "_");

              var junitReporter = new jasmineReporters.JUnitXmlReporter({
                  consolidateAll: true,
                  savePath: testDir,
                  // this will produce distinct xml files for each capability
                  filePrefix: 'test-protractor-' + browserName,
                  modifySuiteName: function (generatedSuiteName) {
                      // this will produce distinct suite names for each capability,
                      // e.g. 'firefox.login tests' and 'chrome.login tests'
                      return 'test-protractor-' + browserName + '.' + generatedSuiteName;
                  }
              });
              jasmine.getEnv().addReporter(junitReporter);
          });
      });
  },

  baseUrl: 'http://localhost:3000',

  // Spec patterns are relative to the current working directory when
  // protractor is called.
  specs: [paths.e2e + '/**/*.js'],

  // Options to be passed to Jasmine-node.
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000
  }
};

The error is:

[13:27:13] E/launcher - Error: Error
    at C:\ws\node_modules\protractor\built\util.js:55:37
    at _rejected (C:\ws\node_modules\q\q.js:844:24)
    at C:\ws\node_modules\q\q.js:870:30
    at Promise.when (C:\ws\node_modules\q\q.js:1122:31)
    at Promise.promise.promiseDispatch (C:\ws\node_modules\q\q.js:788:41)
    at C:\ws\node_modules\q\q.js:604:44
    at runSingle (C:\ws\node_modules\q\q.js:137:13)
    at flush (C:\ws\node_modules\q\q.js:125:13)
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickCallback (node.js:349:13)
[13:27:13] E/launcher - Process exited with error code 100

回答1:

onPrepare is being evaluated in built/util.js in the runFilenameOrFn_ function. The stacktrace unfortunately is not helpful but what this means is that onPrepare has errors. Looking at your onPrepare method, the error is made when assigning the browserName from the browser capabilities. In your code, caps.caps_ is actually undefined. Because caps.caps_ is undefined, caps.caps_.browserName is throwing an error. The capabilities object should be accessed as the following:

browser.getCapabilities().then(capabilities => {
  let browserName = capabilities.browserName.replace(/ /g, "_");

来源：https://stackoverflow.com/questions/40295638/gulp-protractor-error-with-chrome-v54-web-driver-v2-25

标签

google-chrome

gulp

protractor

chrome-web-driver

gulp-protractor

gulp-protractor error with chrome v54 / web driver v2.25

落爺英雄遲暮 — Thu, 16 Jan 2020 21:22:04 +0000

gulp-protractor error with chrome v54 / web driver v2.25 落爺英雄遲暮 2020-01-17 05:22:04

问题

Everything worked fine before chrome's update.

Our protractor configuration is as follows:

exports.config = {
  // Capabilities to be passed to the webdriver instance.
  capabilities: {
    'browserName': 'chrome'
  },

  onPrepare: function () {
      var fs = require('fs');
      var testDir = 'testresults/';
      if (!fs.existsSync(testDir)) {
          fs.mkdirSync(testDir);
      }

      var jasmineReporters = require('jasmine-reporters');

      // returning the promise makes protractor wait for the reporter config before executing tests
      return browser.getProcessedConfig().then(function () {
          // you could use other properties here if you want, such as platform and version

          var browserName = 'browser';
          browser.getCapabilities().then(function (caps) {
              browserName = caps.caps_.browserName.replace(/ /g, "_");

              var junitReporter = new jasmineReporters.JUnitXmlReporter({
                  consolidateAll: true,
                  savePath: testDir,
                  // this will produce distinct xml files for each capability
                  filePrefix: 'test-protractor-' + browserName,
                  modifySuiteName: function (generatedSuiteName) {
                      // this will produce distinct suite names for each capability,
                      // e.g. 'firefox.login tests' and 'chrome.login tests'
                      return 'test-protractor-' + browserName + '.' + generatedSuiteName;
                  }
              });
              jasmine.getEnv().addReporter(junitReporter);
          });
      });
  },

  baseUrl: 'http://localhost:3000',

  // Spec patterns are relative to the current working directory when
  // protractor is called.
  specs: [paths.e2e + '/**/*.js'],

  // Options to be passed to Jasmine-node.
  jasmineNodeOpts: {
    showColors: true,
    defaultTimeoutInterval: 30000
  }
};

The error is:

[13:27:13] E/launcher - Error: Error
    at C:\ws\node_modules\protractor\built\util.js:55:37
    at _rejected (C:\ws\node_modules\q\q.js:844:24)
    at C:\ws\node_modules\q\q.js:870:30
    at Promise.when (C:\ws\node_modules\q\q.js:1122:31)
    at Promise.promise.promiseDispatch (C:\ws\node_modules\q\q.js:788:41)
    at C:\ws\node_modules\q\q.js:604:44
    at runSingle (C:\ws\node_modules\q\q.js:137:13)
    at flush (C:\ws\node_modules\q\q.js:125:13)
    at nextTickCallbackWith0Args (node.js:420:9)
    at process._tickCallback (node.js:349:13)
[13:27:13] E/launcher - Process exited with error code 100

回答1:

browser.getCapabilities().then(capabilities => {
  let browserName = capabilities.browserName.replace(/ /g, "_");

来源：https://stackoverflow.com/questions/40295638/gulp-protractor-error-with-chrome-v54-web-driver-v2-25

标签

Protractor - beforeAll and afterAll undefined

对着背影说爱祢 — Thu, 12 Dec 2019 01:24:44 +0000

Protractor - beforeAll and afterAll undefined 对着背影说爱祢 2019-12-12 09:24:44

问题

I am using Protractor with jasmine. Protractor version is 3.2.2, I found this using the command protractor --version. How to find the jasmine version used by protractor. When I read the updgrade doc, I couldn't find the steps to upgrade jasmine, all I found is to add jasmine2 in configuration file.

My configuration file looks like this

exports.config = {  framework: 'jasmine2', .... }

But I still was not able to use beforeAll and afterAll. Am I missing anything here. Since beforeAll and afterAll are undefined I think the version of jasmine used by protractor is not 2x.

Any help is greatly appreciated.

Thanks.

回答1:

Protractor 3.2.2 as of 20th April 2016 is bundled with Jasmine 2.4

A fresh install of protractor should fetch you the 2.4 version, and you can verify this while looking at the npm install dependency tree log (the npm output after it finished installing a module), search for jasmine in that tree and you should see the 2.4 version being reported.

Also, the correct config to be used is:

framework: 'jasmine'

来源：https://stackoverflow.com/questions/36709893/protractor-beforeall-and-afterall-undefined

标签

Running Gulp-Angular-Protractor without gulp.src

我的梦境 — Wed, 11 Dec 2019 21:49:33 +0000

Running Gulp-Angular-Protractor without gulp.src 我的梦境 2019-12-12 05:49:33

问题

Gulp-Protractor and Gulp-Angular-Protractor can pass args and a config file to protractor.

So why do I need to pass a list of files to gulp?

function runProtractor(done) {
var params = process.argv;
var args = params.length > 3 ? [params[3], params[4]] : [];

gutil.log('arguments: ' + args);

gulp.src(paths.e2eFiles)
  .pipe(protractor({
      configFile: 'protractor.local.conf.js',
      args: args,
      'autoStartStopServer': true,
      'debug': true
  }))
  .on('error', function (err) {
      gutil.log(gutil.colors.red("An error occurred in protractor. Did you start the webdriver?"));
      gutil.log(gutil.colors.red("Run cmd 'start gulp webdriver'."));
      gutil.log(gutil.colors.red('error: ' + err));
      // Make sure failed tests cause gulp to exit non-zero
      throw err;
  })
  .on('end', function () {
      // Close browser sync server
      browserSync.exit();
      done();
  });

} The problem is that protractor are not running the suites but the files in src. Is there a way to call protractor direct?

回答1:

You can leave the gulp.src blank and pass the specs or suites as args, the documentation isn't great at explaining it but I have been able to pass any config file argument that I have tried through gulp as an arg (I think i had an issue with direct connect because it's a boolean and not a string).

gulp.task('e2e', function(cb) {
    gulp.src([]).pipe(protractor({
      configFile: './conf/protractor.conf.js',
      args: [
        '--baseUrl', 'http://localhost/',
        '--maxSessions', 1,
        '--suite', './specs/test-spec.js',
        '--params.environment', 'development'
      ]
    })).on('error', function(e) { throw e })
    .on('end', cb)
  });
};

来源：https://stackoverflow.com/questions/38436507/running-gulp-angular-protractor-without-gulp-src

标签

gulp

gulp-protractor

Protractor - Unable to access element due to fixed Top navigation bar

给你一囗甜甜゛ — Wed, 11 Dec 2019 09:08:52 +0000

Protractor - Unable to access element due to fixed Top navigation bar 给你一囗甜甜゛ 2019-12-11 17:08:52

问题

I'm facing the following issue in protractor with jasmine

Click/mouse hover not working because of fixed top navigation bar in my application. I need to click/perform mouse hover on a web page. Unfortunately that element is displaying behind that fixed navigation bar. So scroll till element present & click by x & y coordinates are not working.

My dependencies are :

protractor version 5.2.2

node 8.9.3

selenium standalone 3.13

chrome driver-2.40

chromebrowser v67

OS- Windows 10

Thanks in advance

回答1:

Try using prototype executeScript

Just try clicking that element from the browser console using id,name or xpath.

For example :

var el = element(by.module('header'));
var tag = browser.executeScript('return arguments[0].click()', el).then(function() {
        expect(something).toMatch(something);
    });

回答2:

Another way, along the same lines as what Bharath Kumar S and knowing JeffC's caveat that this approach is cheating, I had a similar issue where the App-Header kept getting in my way of clicking, and I knew I was willing to never need it (so, for instance, to find other ways to navigate or log out and not check for stuff that was on it). I, therefore, did the following, which solved the problem. Note if you refresh the screen, you have to call it again. Also note I am using a number of functions from https://github.com/hetznercloud/protractor-test-helper, which do what you would expect from their names.

var removeAppHeaderIfAny = async function() {

  //this function hides the app header
  //it is useful to avoid having covers there when Protractor worries that something else will get the click

  let found = false;
  try {
    found = await waitToBeDisplayed(by.className("app-header"), 2000);
  } catch (e) {
    let s: string = "" + e;
    if (s.search("TimeoutError") != 0) flowLog("presumably fine, cover already removed: " + e);
    found = false;
  }
  if (!found) return;

  if (found) {
    let coverElement = await element(by.className("app-header"));
    browser.executeScript(
      "arguments[0].style.visibility='hidden';",
      coverElement
    );
    await waitToBeNotDisplayed(by.className("app-header"), 10000);
  }
  return;
  //note after this is called you will not see the item, so you cannot click it
};

As I look at the code, it strikes me one can probably remove the if (found) and associated brackets at the end. But I pasted in something I know has been working, so I am not messing with that.

As indicated up front, I knew I was willing to forego use of the app-header, and it is a bit crude.

来源：https://stackoverflow.com/questions/51767496/protractor-unable-to-access-element-due-to-fixed-top-navigation-bar

标签

Unable to launch Microsoft edge with protractor

巧了我就是萌 — Wed, 11 Dec 2019 08:31:35 +0000

Unable to launch Microsoft edge with protractor 巧了我就是萌 2019-12-11 16:31:35

问题

Unable to launch edge browser on windows 10 with protractor. edge -Microsoft EdgeHTML 15.15063 downloaded the supported edge driver from https://developer.microsoft.com/en-us/microsoft-edge/tools/webdriver/ i.e Release 15063.

here is my protractor conf file.

module.exports = {

            //seleniumAddress: 'http://localhost:17556',
            keepAlive: true,
            seleniumArgs: ['-Dwebdriver.edge.driver=node_modules/protractor/node_modules/webdriver-manager/selenium/MicrosoftWebDriver.exe'],

            capabilities: {
                'browserName': 'MicrosoftEdge',
                elementScrollBehavior: 1,
                nativeEvents: false 
            },

            framework: 'jasmine2',

            jasmineNodeOpts: {
                defaultTimeoutInterval: 200000,
                isVerbose: true,
            },
        });
    }
};

Error message post launch the e2e:

1:16:58] I/local - Starting selenium standalone server...
[11:16:59] E/launcher - Error: Error: Server terminated early with status 1
    at Error (native)
    at earlyTermination.catch.e (C:\code\e2e\node_modules\selenium-webdriver\remote\index.js:252:52)
    at process._tickCallback (internal/process/next_tick.js:109:7)
Closing report
[11:16:59] E/launcher - Process exited with error code 100
npm ERR! Windows_NT 10.0.15063
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "sanitytests"
npm ERR! node v6.11.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR!  sanitytests: `protractor protractor-sanitytest-conf.js`
npm ERR! Exit status 100
npm ERR!
npm ERR! Failed at the sanitytests script 'protractor protractor-sanitytests-conf.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ??? package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     protractor protractor-sanitytests-conf.js

Could anyone please guide here.

I have updated the node version, now getting unable to create a new service with edge browser.

(node:384) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[14:17:36] I/launcher - Running 1 instances of WebDriver
[14:17:36] I/local - Starting selenium standalone server...
[14:17:37] I/local - Selenium standalone server started at http://192.168.1.4:61872/wd/hub
[14:17:37] E/launcher - Unable to create new service: EdgeDriverService
Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
System info: host: 'DESKTOP-6VHU42F', ip: '192.168.1.4', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_65'
Driver info: driver.version: unknown
[14:17:37] E/launcher - SessionNotCreatedError: Unable to create new service: EdgeDriverService
Build info: version: '3.8.1', revision: '6e95a6684b', time: '2017-12-01T19:05:32.194Z'
System info: host: 'DESKTOP-6VHU42F', ip: '192.168.1.4', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_65'
Driver info: driver.version: unknown
    at Object.checkLegacyResponse (C:\code\e2e\tests\node_modules\selenium-webdriver\lib\error.js:546:15)
    at parseHttpResponse (C:\code\e2e\tests\node_modules\selenium-webdriver\lib\http.js:509:13)
    at doSend.then.response (C:\code\e2e\tests\node_modules\selenium-webdriver\lib\http.js:441:30)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
From: Task: WebDriver.createSession()
    at Function.createSession (C:\code\e2e\tests\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
    at createDriver (C:\code\e2e\tests\node_modules\selenium-webdriver\index.js:170:33)
    at Builder.build (C:\code\e2e\tests\node_modules\selenium-webdriver\index.js:635:14)
    at Local.getNewDriver (C:\code\e2e\tests\node_modules\protractor\built\driverProviders\driverProvider.js:53:33)
    at Runner.createBrowser (C:\code\e2e\tests\node_modules\protractor\built\runner.js:195:43)
    at q.then.then (C:\code\e2e\tests\node_modules\protractor\built\runner.js:339:29)
    at _fulfilled (C:\code\e2e\tests\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (C:\code\e2e\tests\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (C:\code\e2e\tests\node_modules\q\q.js:796:13)
    at C:\code\e2e\tests\node_modules\q\q.js:604:44
    at runSingle (C:\code\e2e\tests\node_modules\q\q.js:137:13)
    at flush (C:\code\e2e\tests\node_modules\q\q.js:125:13)
    at _combinedTickCallback (internal/process/next_tick.js:131:7)
    at process._tickCallback (internal/process/next_tick.js:180:9)
[14:17:37] E/launcher - Process exited with error code 199
npm ERR! code ELIFECYCLE
npm ERR! errno 199
npm ERR! sanitytests: `protractor protractor-sanitytests-conf.js`
npm ERR! Exit status 199
npm ERR!
npm ERR! Failed at the sanitytests script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

回答1:

You have old node version. Update to latest with command:

npm update npm -g

来源：https://stackoverflow.com/questions/47766363/unable-to-launch-microsoft-edge-with-protractor

标签

How to test Pagination feature using Protractor

蹲街弑〆低调 — Wed, 11 Dec 2019 06:38:30 +0000

How to test Pagination feature using Protractor 蹲街弑〆低调 2019-12-11 14:38:30

问题

Please guide me how to navigate through different pages of pagination using Protractor , i followed this blog: http://seleniumhome.blogspot.com/2013/07/how-can-we-automate-pagination-using.html, unfortunately the code is not working. Here is the code from my application:

<div class="vertical-align">
<ul class="pagination no-margins">
<li class="arrow unavailable" ng-class="{unavailable: currentPage === 0 || pagedRowsTotal.length == 0}">
<a class="ng-binding" ng-click="loadPage(0)" ng-bind-html="rsPaginatorText.first">First</a>
</li>
<li class="arrow unavailable" ng-class="{unavailable: currentGroup === 1 || pagedRowsTotal.length == 0}">
<li class="arrow unavailable" ng-class="{unavailable: currentPage === 0 || pagedRowsTotal.length == 0}">
<a class="ng-binding" ng-click="loadPage(currentPage - 1)" ng-bind-html="rsPaginatorText.previous">Previous</a>
</li>
<!-- ngRepeat: page in groupArray track by $index -->
<li class="ng-scope current" ng-class="{current: page === (currentPage + 1)}" ng-repeat="page in groupArray track by $index">
<a class="ng-binding" ng-click="loadPage(page-1)">1</a>
</li>
<!-- end ngRepeat: page in groupArray track by $index -->
<li class="ng-scope" ng-class="{current: page === (currentPage + 1)}" ng-repeat="page in groupArray track by $index">
<a class="ng-binding" ng-click="loadPage(page-1)">2</a>
</li>
<!-- end ngRepeat: page in groupArray track by $index -->
<li class="ng-scope" ng-class="{current: page === (currentPage + 1)}" ng-repeat="page in groupArray track by $index">
<a class="ng-binding" ng-click="loadPage(page-1)">3</a>
</li>
<!-- end ngRepeat: page in groupArray track by $index -->
<li class="ng-scope" ng-class="{current: page === (currentPage + 1)}" ng-repeat="page in groupArray track by $index">
<a class="ng-binding" ng-click="loadPage(page-1)">4</a>
</li>
<!-- end ngRepeat: page in groupArray track by $index -->
<li class="ng-scope" ng-class="{current: page === (currentPage + 1)}" ng-repeat="page in groupArray track by $index">
<a class="ng-binding" ng-click="loadPage(page-1)">5</a>
</li>
<!-- end ngRepeat: page in groupArray track by $index -->
<li class="arrow" ng-class="{unavailable: currentPage === pagedRowsTotal.length -1}">
<a class="ng-binding" ng-click="loadPage(currentPage + 1)" ng-bind-html="rsPaginatorText.next">Next</a>
</li>
<li class="arrow" ng-class="{unavailable: currentGroup === groupsTotal}">
<li class="arrow" ng-class="{unavailable: currentPage === pagedRowsTotal.length -1}">
<a class="ng-binding" ng-click="loadPage(pagedRowsTotal.length - 1)" ng-bind-html="rsPaginatorText.last">Last</a>
</li>
</ul>

This is what i tried, but receiving an error:

this.getPaginationsize = element.all(by.repeater('page in groupArray track by $index'));

summaryPage.getPaginationsize.getSize().then(function (pagination) {
            if (pagination > 0) {

                for (var i = 0; i < pagination; i++) {
                    summaryPage.getPaginationsize.get(i).click();
                }
            } else {
                console.log('Pagination not exists');
            }
        });

Failed: Cannot convert object to primitive value

回答1:

summaryPage.getPaginationsize.getSize() method will return an Object with height and width of a webelement. Instead you need to use summaryPage.getPaginationsize.count() to get the total number of pageSize.

Reference:

getSize() : http://www.protractortest.org/#/api?view=webdriver.WebElement.prototype.getSize count() : http://www.protractortest.org/#/api?view=ElementArrayFinder.prototype.count

来源：https://stackoverflow.com/questions/46183341/how-to-test-pagination-feature-using-protractor

标签

Protractor - Change Browser Capabilities at RunTime

依然范特西╮ — Sat, 07 Dec 2019 00:39:14 +0000

Protractor - Change Browser Capabilities at RunTime 依然范特西╮ 2019-12-07 08:39:14

问题

Is there a way to change the browser capabilities within beforeEach of the protractor suite. I need to set the Capabilities.name attribute before each spec execution.

回答1:

To create separate instances of the desired capabilities, such as capabilities.name, you will want to try the multiCapabilities option available via Protractor. An example would look similar to what is below and reside in the conf.js file. This allows you to submit a unique name for each test session.

  onPrepare: function(){
  var caps = browser.getCapabilities()
  },

  multiCapabilities: [{
    browserName: 'firefox',
    version: '32',
    platform: 'OS X 10.10',
    name: "firefox-tests",
    shardTestFiles: true,
    maxInstances: 25
  }, {
    browserName: 'chrome',
    version: '41',
    platform: 'Windows 7',
    name: "chrome-tests",
    shardTestFiles: true,
    maxInstances: 25
  }],

A complete example of this can be seen here:

https://github.com/saucelabs-sample-test-frameworks/JS-CucumberJS-Protractor3.0/blob/master/conf.js

回答2:

Here are the sauceLabs capabilities: https://wiki.saucelabs.com/display/DOCS/Test+Configuration+Options

When you don't specify a Capabilities.name it looks like sauceLabs reports each test formatted as browserName:specFilename by default.

回答3:

You can't change the capabilities in beforeEach() (Jasmine hook) or onPrepare() (Protractor conf.js) because the browser instance has already been created and webdriver session has been started with the capabilities already sent to the Selenium server.

Desired capabilities are set in the conf.js under Capabilities or Multicapabilities. You could set them at runtime by getting a variable before exporting in conf.js.

One common way to do this is to set the capability using an environment variable, for example:

Capabilities: {
  browserName: process.env.SELENIUM_BROWSER
}

You can set variables to be used in capabilities in beforeLaunch() but this executes one time only, before any specs are read.

There is an excellent summary of the Protractor / Jasmine hooks here:
http://timothymartin.azurewebsites.net/protractor-before-and-afters/

I have not yet identified a way (without modifying Protractor source) to change capabilities dynamically on a per-spec or per-suite basis.

来源：https://stackoverflow.com/questions/34823248/protractor-change-browser-capabilities-at-runtime

标签

protractor

gulp-protractor

'$' selector in Protractor

假装没事ソ — Fri, 06 Dec 2019 21:40:59 +0000

'$' selector in Protractor 假装没事ソ 2019-12-07 05:40:59

问题

I have seen in many examples like this $('.selector') and I am also using this. So what this $ variable does. This is what I got from the protractor docs.

Calls to $ may be chained to find elements within a parent.

There is no example in docs which use $ alone. We are using $ to chain with element selector.

Also $('.selector') itself is an element, when we does this element($('.selector')), it is an error.

So how to use this $ selector in protractor. Does it have all the features of JQuery $. I tried $('.selector').children which says children is not a function.

Any help is greatly appreciated.

Thanks!

回答1:

That looks like jQuery syntax but it is not, it's part of Protractor. That's why .children is throwing an error because we're not actually using jQuery. $ is a shorthanded version of element(by.css()) i.e.

$('my-css'); is the exact same as element(by.css('my-css'));

They also have $$ which is the same as element.all(by.css())

Despite the lack of documentation, it does not have to be used for chaining to find child elements. i.e. using Julie's protractor demo (I modified the example):

describe('Protractor Demo App', function() {
  it('read the header', function() {
    browser.get('http://juliemr.github.io/protractor-demo/');
    $('h3').getText().then(function (val) {
      console.log(val);
    });
  });
});

That prints out the title of the h3 element that I located. The $ and $$ are simply a shorthand for css selectors.

Source: here for $$, here for $, and here for more

Also this is a nice document I found (though it does not mention the use of $$ : http://luxiyalu.com/protractor-locators-selectors/

回答2:

We made updates to the Protractor's API for $. Also, there are several places in Protractor's specs that use chained $. See below (from spec/async_spec.js):

  it('should work with synchronous actions', function() {
    var increment = $('#increment');
    increment.$('.action').click();

    expect(increment.$('.val').getText()).toEqual('1');
  });

回答3:

This is the correct API doc for $:

"Shortcut for querying the document directly with css. element(by.css('.abc')) is equivalent to $('.abc')"

http://www.protractortest.org/#/api?view=build$

来源：https://stackoverflow.com/questions/36791397/selector-in-protractor

标签

'$' selector in Protractor

旧时模样 — Thu, 05 Dec 2019 02:33:17 +0000

'$' selector in Protractor 旧时模样 2019-12-05 10:33:17

I have seen in many examples like this $('.selector') and I am also using this. So what this $ variable does. This is what I got from the protractor docs.

Calls to $ may be chained to find elements within a parent.

There is no example in docs which use $ alone. We are using $ to chain with element selector.

Also $('.selector') itself is an element, when we does this element($('.selector')), it is an error.

So how to use this $ selector in protractor. Does it have all the features of JQuery $. I tried $('.selector').children which says children is not a function.

Any help is greatly appreciated.

Thanks!

$('my-css'); is the exact same as element(by.css('my-css'));

They also have $$ which is the same as element.all(by.css())

Despite the lack of documentation, it does not have to be used for chaining to find child elements. i.e. using Julie's protractor demo (I modified the example):

describe('Protractor Demo App', function() {
  it('read the header', function() {
    browser.get('http://juliemr.github.io/protractor-demo/');
    $('h3').getText().then(function (val) {
      console.log(val);
    });
  });
});

That prints out the title of the h3 element that I located. The $ and $$ are simply a shorthand for css selectors.

Source: here for $$, here for $, and here for more

Also this is a nice document I found (though it does not mention the use of $$ : http://luxiyalu.com/protractor-locators-selectors/

We made updates to the Protractor's API for $. Also, there are several places in Protractor's specs that use chained $. See below (from spec/async_spec.js):

  it('should work with synchronous actions', function() {
    var increment = $('#increment');
    increment.$('.action').click();

    expect(increment.$('.val').getText()).toEqual('1');
  });

This is the correct API doc for $:

"Shortcut for querying the document directly with css. element(by.css('.abc')) is equivalent to $('.abc')"

http://www.protractortest.org/#/api?view=build$

来源：https://stackoverflow.com/questions/36791397/selector-in-protractor

标签