Timeline for Speeding up end-to-end tests
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 30, 2018 at 2:52 | history | tweeted | twitter.com/StackSQA/status/979551933055848448 | ||
| Mar 29, 2018 at 16:15 | vote | accept | alecxe | ||
| Mar 29, 2018 at 0:28 | answer | added | Vishal Aggarwal | timeline score: 8 | |
| Aug 4, 2017 at 0:35 | vote | accept | alecxe | ||
| Mar 29, 2018 at 16:15 | |||||
| Jul 11, 2017 at 4:55 | answer | added | A.A.A | timeline score: 2 | |
| Jul 11, 2017 at 2:43 | history | edited | alecxe | CC BY-SA 3.0 |
edited title
|
| Jul 10, 2017 at 21:13 | comment | added | alecxe | @YuZhang correct, from readability point of view. Protractor itself is advertised as "You no longer need to add waits and sleeps to your test. Protractor can automatically execute the next step in your test the moment the webpage finishes pending tasks, so you don’t have to worry about waiting for your test and webpage to sync.". But, in reality, we still have to add waits here and there.. Thanks. | |
| Jul 10, 2017 at 21:11 | comment | added | Yu Zhang | "By adding explicit waits, the tests become less readable and the test flow less understandable and clean;" from code review point of view, I guess? | |
| Jul 10, 2017 at 19:59 | history | asked | alecxe | CC BY-SA 3.0 |