Closed
Bug 533539
Opened 15 years ago
Closed 14 years ago
Implement a script to sync smoketest/bft results on the couchdb with litmus
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: whimboo, Unassigned)
References
Details
We are able to send reports to couchdb now. Only support for restart tests is missing. That will be done in bug 533227. To lower the amount of work we have to do for release testing, which means to enter results manually into litmus we should have a script which automatically synchronizes the results right out of the couchdb with litmus.
Reporter | ||
Updated•15 years ago
|
Whiteboard: [qae-p1]
Comment 1•15 years ago
|
||
Just finished breaking up all this logic so you can do this. pull from mikeal/mozmill/tree/reports and it should be clear how to go about implementing this by looking at my code for the restart tests.
Comment 2•15 years ago
|
||
Sorry, that last comment was made for a different bug. It *might* be easier to do this the opposite way of the one proposed in this bug. Pull results out of Litmus in to CouchDB and create a few new pages to view the results :)
Reporter | ||
Comment 3•15 years ago
|
||
(In reply to comment #2) > It *might* be easier to do this the opposite way of the one proposed in this > bug. Pull results out of Litmus in to CouchDB and create a few new pages to > view the results :) Why should that be easier? You would have to write a reporting module for Litmus AND the sync script. We already have everything in place to report to brasstacks. We should use this feature because we always wanna report to brasstacks and only sync special reports (user needs permissions to do that) with Litmus.
Reporter | ||
Comment 4•14 years ago
|
||
WONTFIX, we don't need this feature anymore. We do it manually and it works fine.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
Reporter | ||
Updated•14 years ago
|
Whiteboard: [qae-p1]
Assignee | ||
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•