Auto-tools/Projects/Signal From Noise/Meetings/2012-05-17

Previous Action Items

• find what pages we can consider reliable
  • define what "reliable" is
• triangulate
• [christina] - give jeads/ctalbert/jmaher a set of pages that are just too noisy and operating systems
• local TBPL (contact: edmorley)

Datazilla

Round Table

ctalbert's official list of goals for SfN this quarter

• a production system slurping up data from talos deployed (staging env is fine since we know we won't get sec review done in time)
  • Owner: Jeads
  • Next steps: https://www.pivotaltracker.com/projects/540155#!/epics/109709

• ability on this production system to accept data from non-talos projects
  • Owner: ??
  • Next steps: https://www.pivotaltracker.com/epic/show/109709

• the UI we largely have now
  • Owner: ??
  • Next steps:

• Metrics for determining page-centric "did my test pass or not" for at least one suite dromaeo and ts_paint
  • Owner: Christina/Jeads
  • Next steps: Iterate on the development data. We're going to go ahead with the ~26 "good" pages in tp5. It's going to be awhile before we have representative data for dromaeo and wading in on ts_paint could introduce a whole new set of variables that send us into the talos briar patch.
    • [jeads] Build SQL queries to pull out representative data for the ~26 "good" pages in tp5
    • [christina and jeads] Develop the input data set for analysis in R
    • [christina and jeads] Identify an outlier that is outside an allowable range
    • [christina] Develop an allowable range for a test result for each of the ~26 pages
    • [christina] Determine a score for a changeset across the entire test suite. This could be as simple as 0 or 1 for each page, that gets added up across all pages and platforms. So 24/26 would indicate 24 pages were in the allowable range 2 were not for one platform. We will not know the best way to do this until we wade into the data.
    • [everyone] Determine a way to convert the test suite score into a pass, fail, or undetermined result for a given changeset.

• a stage tbpl system mocking the Yes/No/Maybe interaction
  • Owner: ??
  • Next steps: assert we can mock up tbpl to gather data post test completion, will mozilla be ok with that?
    • tbpl can do this: POST {'changeset': 31415926535, 'testname': 'dromaeo', 'platform': 'win7'} http://10.8.73.29/views/api/test_results
    • and recieve this: {'result':'PASS', 'tests': {'passed': 98, 'failed': 0, 'maybe': 2}, 'details': [{'k0s.org': {'actual': 2.71, 'expected': [2.75, 3.21]}, {'askjeads.com': {'actual': 99, 'expected': [88, 98]}]}

• We will have fixed the pages accessing web in tp5 and re-release the tp5 pageset with the new non-web touching pages
  • Owner: jmaher
  • Next steps: write a cleanup script, run webpages through a cleanup script, verify the pages are clean, talk to releng

• Convert all page cycle extension based tests to row-major style.
  • Owner: jmaher
  • Next steps: run tdhtml, tsvg, tsvg_opacity, tsspider, tscroll, a11y in staging, create graph server definitions for new test types, start side by side staging.