Auto-tools/Projects/Signal From Noise/Meetings/2012-05-17: Difference between revisions
< Auto-tools | Projects | Signal From Noise | Meetings
Jump to navigation
Jump to search
| Line 38: | Line 38: | ||
* We will have fixed the pages accessing web in tp5 and re-release the tp5 pageset with the new non-web touching pages (i.e. we are *not* waiting for google and their page set - we should start this now - this is fixed and checked-in, and on releng's list for deployment in Q3). | * We will have fixed the pages accessing web in tp5 and re-release the tp5 pageset with the new non-web touching pages (i.e. we are *not* waiting for google and their page set - we should start this now - this is fixed and checked-in, and on releng's list for deployment in Q3). | ||
** Owner: | ** Owner: jmaher | ||
** Next steps: | ** 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. (Stop analysis on row vs. column, and just make the call to go with row. This should be largely deployed by end of Q2) | * Convert all page cycle extension based tests to row-major style. (Stop analysis on row vs. column, and just make the call to go with row. This should be largely deployed by end of Q2) | ||
** Owner: | ** Owner: jmaher | ||
** Next steps: | ** 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. | ||
= Action Items = | = Action Items = | ||
Revision as of 17:26, 16 May 2012
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)
Metric Calculations
Datazilla
Page Specific Views
Compare Talos Functionality
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: ??
- Next steps:
- ability on this production system to accept data from non-talos projects
- Owner: ??
- Next steps:
- 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 (and that suite *won't* be tp5)
- Owner: ??
- Next steps:
- a stage tbpl system mocking the Yes/No/Maybe interaction
- Owner: ??
- Next steps:
- We will have fixed the pages accessing web in tp5 and re-release the tp5 pageset with the new non-web touching pages (i.e. we are *not* waiting for google and their page set - we should start this now - this is fixed and checked-in, and on releng's list for deployment in Q3).
- 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. (Stop analysis on row vs. column, and just make the call to go with row. This should be largely deployed by end of Q2)
- 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.