VTK/SoftwareQuality/VTKDashboardHackathon1: Difference between revisions

From KitwarePublic
< VTK
Jump to navigationJump to search
Line 29: Line 29:
==Process==
==Process==
===Define===
===Define===
What do we want to accomplish?
===Measure===
===Measure===
Failing Expected Nightly Tests
Failing Expected Nightly Tests

Revision as of 17:53, 22 February 2013

The first VTK Dashboard Hackathon is scheduled for February 27, 2013. The purpose of this hack-a-thon is to drive the number of recurring, failing test defects to 0 on the VTK Nightly Expected dashboard.

Logistics

  • Location: Kitware, Clifton Park
  • Google Hangout: TBD
  • Beer celebration: TBD

Agenda

Note: all times are preliminary and flexible

Location: KHQ21 Conference Room

  • 9:00 - Review/modify agenda
  • 9:15 - Review/modify goals
  • 9:30 - Establish baseline
  • 9:45 - Assignments
  • 10:00 - Hack, hack, submit reviews

Location: KHQ21 Auditorium

Process

Define

What do we want to accomplish?

Measure

Failing Expected Nightly Tests

Analyze

This table summarize the failing tests and preliminary diagnosis.

Improve

Gerrit topics to fix failing tests.

Control

How to we keep things green?