You can use Protractor debug/pause feature to pause the e2e run which will ultimately leave the browser open: more info here To do so, add this line on your protractor test before the failing one browser.pause(); There is also a very useful tool called elementor that you may want to take a look later on.
I can currently set download path location Chrome capabilities: { ‘browserName’: ‘chrome’, ‘platform’: ‘ANY’, ‘version’: ‘ANY’, ‘chromeOptions’: { // Get rid of –ignore-certificate yellow warning args: [‘–no-sandbox’, ‘–test-type=browser’], // Set download path and avoid prompting for download even though // this is already the default on Chrome but for completeness prefs: { ‘download’: { ‘prompt_for_download’: …
You can get an indexed element from an array returned with // Get the 5th element matching the .dfdf css selector element.all(by.css(‘.dfdf’)).get(4).sendKeys(‘foo’);
Install protractor and grunt-protractor-runner from npm: npm install protractor grunt-protractor-runner –save-dev Create a config file for protractor (protractor.conf.js), change specs and baseUrl to your test files and test server: exports.config = { seleniumAddress: ‘http://localhost:4444/wd/hub’, specs: [‘test/e2e/*_test.js’], baseUrl: ‘http://localhost:9001’ //default test port with Yeoman } Update your Gruntfile.js, add the following after the karma task: protractor: …
Hi we can have a discussion over it but as far as selenium vs protractor goes: SELENIUM Works great even if it’s angular JS website, only we have to deal with synchronization issue. If you can handle then no disadvantage. Selenium is very rich in automation, i.e, it’s in the market for years and very …
I solved this with –standalone flag: webdriver-manager start –standalone
I had met same issue. First I remove ts-node and typescript from package.json. then, npm install ts-node –save-dev npm install typescript -g npm install typescript –save-dev
As of the most recent Protractor (1.6.1 as of this writing), the syntax changed a bit: var row = results[randomNum].element(by.xpath(‘..’)); (use element() instead of findElement()).
This is a rather common problem in test automation with selenium. Here are the common solutions: make sure the element you want to click is actually visible. Sometimes you need to make extra actions on a page to make the element visible. For example, open up a dropdown for an option to appear or open …