1207251 - Decide whether to remove/replace the Jasmine UI tests

Status: RESOLVED DUPLICATE of bug 1364045

(Tree Management :: Treeherder, defect, P4)

Description

[Ed Morley [:emorley]]

Broken out from bug 1206697.

https://github.com/mozilla/treeherder/pull/981#issuecomment-142363844
> :camd wrote:
> Now that this comes up, I'm questioning the jasmine tests value. We haven't written new ones in ages and who knows if we ever will. I introduced these ages ago and wrote some tests, but as our UI changed, I kept updating and removing invalid ones.
> 
> We should probably either write some tests that have value, or just remove this stuff entirely. I mean, it WOULD be nice, if we had useful tests. :) But perhaps the selenium tests QA is going to write are better at covering things?

Comment 1

[Ed Morley [:emorley]]

I was under the impression all of our current UI tests use Jasmine. If we are to remove them, we'll need to have some other tests in place first (eg the Selenium tests actually need to be in our repo and run on Travis). The UI tests do actually fail occasionally in response to regressions (don't forget Mauro added some more after his refactor), so I think they have at least some value for the moment :-)