Actions
Bug #13456
closed
[Workbench] Fix flaky integration tests
Added by Tom Morris almost 6 years ago. Updated about 4 years ago.
Status:
Closed
Priority:
Low
Assigned To:
-
Category:
-
Target version:
-
Story points:
-
Updated by Lucas Di Pentima almost 6 years ago
- Assigned To set to Lucas Di Pentima
Updated by Lucas Di Pentima almost 6 years ago
- Target version changed from 2018-05-23 Sprint to 2018-06-06 Sprint
Updated by Lucas Di Pentima almost 6 years ago
- Assigned To changed from Lucas Di Pentima to Tom Clegg
Updated by Tom Clegg almost 6 years ago
- Target version changed from 2018-06-06 Sprint to 2018-06-20 Sprint
Updated by Tom Clegg almost 6 years ago
cae5f7def9dae9caf9056bc3bb77ca801cfa2229 doesn't seem to have helped.
Updated by Tom Clegg almost 6 years ago
Investigation revealed:
- Tests fail when phantomjs crashes.
- It's not a specific test or class that causes phantomjs to crash.
- Some known crashing bugs in Phantomjs have been fixed in version 2, but some work is required to make our test suite compatible with version 2. Capybara::Poltergeist::DeadClient when JS errors are thrown
- PhantomJS is EOL/deprecated/abandoned.
Updated by Tom Clegg almost 6 years ago
- Status changed from In Progress to New
- Target version deleted (
2018-06-20 Sprint)
Updated by
Updated by Peter Amstutz about 4 years ago
- Priority changed from Normal to Low
- Assigned To deleted (
Tom Clegg) - Status changed from New to Closed
Actions