Timeline for How to avoid flakey E2E selenium tests?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 14, 2015 at 13:15 | answer | added | masood ghz | timeline score: 5 | |
| Aug 13, 2015 at 0:35 | history | tweeted | twitter.com/#!/StackSQA/status/631624973761835009 | ||
| Aug 12, 2015 at 9:21 | comment | added | Philipp Claßen | @dzieciou Yes, I know the article, and there is certainly a lot of truth in it. | |
| Aug 11, 2015 at 20:34 | answer | added | Julian | timeline score: 5 | |
| Aug 11, 2015 at 19:21 | comment | added | dzieciou | Well, from my short experience, any end-to-end tests will be flakey, see Google take on that: googletesting.blogspot.com/2015/04/… You can get a better ROI from making part of your tests on lower levels, e.g. on backend API. | |
| Aug 11, 2015 at 19:03 | review | First posts | |||
| Aug 12, 2015 at 11:27 | |||||
| Aug 11, 2015 at 19:01 | history | asked | Philipp Claßen | CC BY-SA 3.0 |