Automated Testing Summit 2019

Revision as of 20:17, 5 September 2019 by Tim Bird (talk | contribs)
Jump to: navigation, search

This is a public planning page for the Automated Testing Summit

Please see:

2019 meeting

Coordinated by: Tim Bird

Mailing list

Inter-project discussions on Automated Testing occur on the "Automated Testing" mailing list of the Yocto Project

Date and Venue

  • Location: Lyon, France
  • Venue: Lyon Convention Center, 50 Quai Charles de Gaulle
  • Date: October 31, 2019
  • Rooms: (To be announced)
  • Time: (To be announced)

Attendance is by open to the public, and we are projecting the attendee fee to be $250, with this fee waived for speakers.

Summit Pre-planning

Here is a list of action items to do to prepare for the summit:

  • organize program committee (in progress)
  • get sponsors
    • create sponsorship prospectus (almost done)
    • contact candidate sponsors (in progress)
  • hold "Call for Proposals"
    • need to determine CFP dates (done)
  • determine agenda
    • organize program committee (in progress)
  • advertise for attendees
  • reserve venue, catering, AV rentals (done)
  • create signage, web site, registration system

For private planning information, see the private planning wiki page

Call for Presentations

  • CFP Open: Tuesday, May 28
  • CFP Close: Friday, August 13
  • Notifications Out: September 2
  • Schedule Out: September 4
  • Slides Due: October 24, 2019
  • Event Date: October 31, 2019

Suggested Topics

  • Board Farms and Test Labs - hardware, software, useful practices
  • Layers and Interfaces - components of your automated CI loop and protocols between them
  • Results Reporting - results aggregation, visualization, notifications, etc.
  • Defining standards - propose or discuss conventions for test definitions, results formats, layer interoperability (e.g. protocols), etc.
  • Existing Projects - describe your test system or framework and any challenges you overcame or that are still outstanding
  • Scalability - supporting big data, or handling distributed builds or tests
  • Ease of use - making testing and test development accessible to non-QA folk (developers, end-users)

Pre-meeting work

Here's what Tim thinks we need to do:

  • Refine the test stack reference diagram
  • Organize committees for specific APIs
    • designate a head for each committee


Sponsorship is being provided by:

  • (To be announced)


(To be announced)

Summit Artifacts

(To be uploaded after the event)

Action items from meeting

Action items: