Changes

Jump to: navigation, search

Auto-tools/Projects/OrangeFactor

1 byte removed, 13:39, 23 October 2014
Update bug links after component move & rename "War on Orange" + "Orange Factor" to "OrangeFactor"
== Status ==
The [http://brasstacks.mozilla.com/orangefactor/ War on Orange OrangeFactor] web app] provides a variety of ways to view data on buildbot orange failures. File bugs under [https://bugzilla.mozilla.org/enter_bug.cgi?product=TestingTree+Management&component=Orange%20Factor Testing/Orange FactorOrangeFactor Tree Management::OrangeFactor].
We were taking [[Auto-tools/Projects/WarOnOrangeOrangeFactor/Meetings|minutes of meetings]] early on in the project, but since then we are tracking features and bugs in [https://bugzilla.mozilla.org/buglist.cgi?list_id=3163513;resolution=---;query_format=advanced;&component=Orange%20Factor;OrangeFactor&product=Testing Tree+Management Bugzilla].
For an overview, see [http://people.mozilla.com/~mcote/war-on-orange/war-on-orange-paper-testistanbul.pdf this paper] and the accompanying [http://people.mozilla.com/~mcote/war-on-orange/war-on-orange-testistanbul-slides-presentation.pdf slides], prepared for the TestIstanbul 2012 conference.
== History ==
These projects are deprecated and replaced by the new War on Orange/Orange Factor OrangeFactor application.
'''Topfails'''
source: http://github.com/jmaher/Orange-Factor
[[Auto-tools/Projects/WarOnOrangeOrangeFactor/InstallationInstructions|Installation instructions]]
[https://bugzilla.mozilla.org/buglist.cgi?resolution=---&component=Orange%20FactorOrangeFactor&product=Testing Tree+Management bugs]
== Architecture ==
=== Development & Deployment ===
The Orange Factor OrangeFactor web app can be run locally. See the instructions at:
https://hg.mozilla.org/automation/orangefactor/file/tip/README.txt
* identify interesting patterns in failures; some failures may occur more frequently on certain OS's, build types, architectures, or other factors; by providing views which can track oranges across a range of factors, we might be able to provide developers with data that would help them reproduce failures or give them insight into their cause
* identify overall trends in orange occurrences, already part of the [http://jmaher.couchone.com/orange_factor/_design/woo/orange.html legacy Orange Factorapp]; this can help track the 'orangeness' of a product over time, and can help measure the helpfulness of orange-fixing activities
== Dashboard Views ==
A list of dashboard views that may be interesting. We're currently using Orange Factor OrangeFactor as a platform to experiment with views.
* {{done|display}} of overall orange factor over time
The amount of information yielded from the parsed logs is vast. The raw data will be noisy and the trends will not be easily discerned. So statistical analysis should be used to manipulate the data and seek insight into trends.
[[Auto-tools/Projects/WarOnOrangeOrangeFactor/Statistics|War On Orange Statistics]]
== How Tinderbox Stores Its Data ==
== ElasticSearch Queries ==
The log metadata is all stored in ElasticSearch, see the [[Auto-tools/Projects/WarOnOrangeOrangeFactor/ElasticSearch|ElasticSearch]] page for details on querying this database.
== Attacking Oranges ==
Canmove, confirm
1,126
edits

Navigation menu