Difference between revisions of "Selenium"
From CitconWiki
Jump to navigationJump to searchAdinnaplus (talk | contribs) |
Adinnaplus (talk | contribs) |
||
Line 16: | Line 16: | ||
* transfer selenium tests to headless browser / api tests (e.g AngularJS, Protractor) | * transfer selenium tests to headless browser / api tests (e.g AngularJS, Protractor) | ||
* Apache Mesos | * Apache Mesos | ||
+ | |||
+ | |||
+ | == Selenium Flaky Tests == | ||
+ | '''Did anyone of us tried tracking the failures of a test and doing an analysis on that, such as to see the frequency of flakiness?''' | ||
+ | * rerun failed tests | ||
+ | * Atlassian Bamboo | ||
+ | * custom JUnit runner to parse build results (and store in DB or just Logger) | ||
+ | |||
+ | == Selenium Fixing reds (failed tests) == | ||
+ | '''One of the problems is that test builds are red and nobody seems to care...''' | ||
+ | * measuring and visualizing | ||
+ | * ownership on tests | ||
+ | * set a smaller goal of the day |
Revision as of 06:33, 12 September 2015
Selenium Grid and Selenium
Selenium Grid
Is it worth switching to Selenium Grid?
Selenium Grid Benefits:
- for cross browsers, there are other options as well
- parallel testing
Latest version: 2.47 (2 people in the room use the latest version)
Ideas on using Selenium Grid with other configs:
- !Gradle
- SauceLabs / Keynote (Keynote costs more)
- transfer selenium tests to headless browser / api tests (e.g AngularJS, Protractor)
- Apache Mesos
Selenium Flaky Tests
Did anyone of us tried tracking the failures of a test and doing an analysis on that, such as to see the frequency of flakiness?
- rerun failed tests
- Atlassian Bamboo
- custom JUnit runner to parse build results (and store in DB or just Logger)
Selenium Fixing reds (failed tests)
One of the problems is that test builds are red and nobody seems to care...
- measuring and visualizing
- ownership on tests
- set a smaller goal of the day