Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve setting up Sizzle for Selenium tests.
Something releated to AMD broke our way of injecting Sizzle into Galaxy for Selenium tests. This is a much better way that seems to work - just use jQuery ($) as Sizzle if it is available. Avoids an external dependency and another page fetch per test as well as fixing the problem. Add a test case that just tests the sizzle stuff works on its own. It will be a clear indiciation what is broken if there are related regressions in the future.
- Loading branch information
Showing
2 changed files
with
24 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
from .framework import SeleniumTestCase | ||
from .framework import selenium_test | ||
|
||
|
||
class SizzleLoadingTestCase(SeleniumTestCase): | ||
|
||
@selenium_test | ||
def test_sizzle_loads(self): | ||
self.home() | ||
self.wait_for_sizzle_selector_clickable("div") |