cnishina on selenium4
chore(release): bumpb version t… (compare)
I am in a decision-making situation to either use Protractor or Selenium to create test automation framework for two apps, one is Angular-based, another is Vue JS based.
Advantages of using Protractor:
Comes bundles with Aungular app, no need to add exrta dependency
Supports more element locating mechanisms by providing methods like filter() and cssContainingText()
Main reason for using Protractor was because prtractor had its own locator types (like ng-model, etc) in order to handle elements in ealier version of Angular apps. However after Angular 2, those locators types have become irrelevant and now protractor uses locators just like in Selenium
I also have expert level knowledge in Selenium and Java
What should be my parameters to select either Protractor or Selenium to create a test automation framework and automate integration test cases? Is execution faster in Protractor because it uses scripting language?
.specfile? I could reproduce this in a clean project.
$('div.someInvalidElement').click()in a separate helper file.
myPromise.then(() => $('div.someInvalidElement').click())
.spec, but directly to the
it()function, not the exact line WITHIN
hey all, my google fu is failing me and I'm not asking the right query. I overheard some colleagues following the antipattern of physically opening the window to test the URL. They were further challenged that the property would not properly open the window as
this._linkUrl was only loaded in the upper validation environments.
The team is trying to test a template that produces a
<button> binding to the
[click] and calls a method that calls
I'm trying to get them to test the value from the component, not opening windows, switching to the new window, and attempting to read the location. But I'm not speaking to the specifics of their problem, but I'm reaching out to the channel hoping for help in pointing best pattern for the team to review and implement.
--async-stack-tracesdidn't help this specific protractor problem. (For future searchers, this was using protractor 5.4.2) @cnishina any insight?