No visual indication that test-cases have been submitted correctly



Other Applications
QA Companion
9 years ago
5 years ago


(Reporter: shirish, Unassigned)


Firefox Tracking Flags

(Not tracked)




9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a2pre) Gecko/20090917 Namoroka/3.6a2pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2a2pre) Gecko/20090917 Namoroka/3.6a2pre Mozilla QA companion 1.2.1

As of right now, there is just no way for a user to know if the test-case submission went alright or not. 

Reproducible: Always

Steps to Reproduce:
1.Install QA companion 1.2.1 from
2.Start doing test-cases
3.Click on either of the three states, pass, fail or unclear
Actual Results:  
After waiting for sometime you get the next test-case

Expected Results:  
It should give some sort of visual indication that the test-case was successfully submitted.
You should be able to see a green flash on progression of a testcase advancement indicating a successful submit as of bug 509507.

Can you confirm if you see that?
Thanks for filing shirish, The green flash only happens when we advance test subgroups. We should add something for submitting each testcase (Clint suggested a label and a smaller version of a star from the stats tab, that time out). Though if we move on to the next testcase before we find out if it was successful, this would be a bad idea.
Ever confirmed: true
If we wait for a successful submit first and then we advance the test case, we introduce yucky bug 517471 but we know for sure that the submit was successful so we have our green flash indication.

If we put in a fix for bug 517471 and advance the test case but do a background submission, I than see a need for a separate visual indicator. 

I say this bug is dependent on what we do with bug 517471.


9 years ago
Depends on: 517471

Comment 4

5 years ago
Litmus has been replaced by MozTrap. 

If we want an extension to integrate with MozTrap, it would be better to start from scratch with a new extension rather than trying to shoehorn that functionality into the >5 year old QAC.
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.