Need a Selenium javascript sanity test
Bug #1187576 reported by
David Lyle
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Medium
|
George Peristerakis |
Bug Description
There have been more than one occasion where javascript python-compression has been broken when new libraries are included. There needs to be a better javascript sanity test to verify that core behavior still works.
Changed in horizon: | |
status: | New → Confirmed |
Changed in horizon: | |
importance: | Undecided → Medium |
Changed in horizon: | |
assignee: | nobody → George Peristerakis (george-peristerakis) |
Changed in horizon: | |
status: | Confirmed → In Progress |
Changed in horizon: | |
status: | In Progress → Fix Committed |
Changed in horizon: | |
milestone: | none → icehouse-1 |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | icehouse-1 → 2014.1 |
To post a comment you must log in.
The problem here is that while running the selenium tests, the settings variable COMPRESS_ENABLED is set to False. There's 2 ways of solving this:
1. Enable the variable COMPRESS_ENABLED for all the tests, but this will slow the test down.
2. Enable it manually for selenium test only.