89
edits
QA/Mozmill Test Automation/Dashboard/Roadmap/0.4: Difference between revisions
QA/Mozmill Test Automation/Dashboard/Roadmap/0.4 (view source)
Revision as of 02:48, 18 May 2011
, 18 May 2011→Technical Background
| Line 51: | Line 51: | ||
** I will try to use something that has been used before. Likely, sammy.js views that allow for all the functionality listed in the functionality section. | ** I will try to use something that has been used before. Likely, sammy.js views that allow for all the functionality listed in the functionality section. | ||
; Unknowns | ; Unknowns | ||
* Results are currently | * Results are currently received (and stored) based on the report they were submitted with. However, we want to show the user information aggregated per test function. This aggregation as well as filtering /searching (by local, language, operating system ect.) needs to happen in real time. | ||
** Ideally we would filter and search the data with elastic search and then run a map reduce in order to aggregate this data. The systems are not usually designed for this, elastic search doesn't output large quantities of data in real time (with the current database, looking through all data takes multiple seconds) | ** Ideally we would filter and search the data with elastic search and then run a map reduce in order to aggregate this data. The systems are not usually designed for this, elastic search doesn't output large quantities of data in real time (with the current database, looking through all data takes multiple seconds) | ||
** Another option is to duplicate all the data per function. We wouldn't have to map the data of reports to functions in that case but we would have a much larger database with a lot of extra data in it. | ** Another option is to duplicate all the data per function. We wouldn't have to map the data of reports to functions in that case but we would have a much larger database with a lot of extra data in it. | ||