CITCONEurope2013Sessions

From CitconWiki
Revision as of 09:42, 6 October 2013 by Jtf (Talk | contribs) (add links for missing sessions from Turin)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

CITCON Europe 2013 Turin Sessions

Back to the Main Page

10:00 Topics

  1. Are we doing improvement wrong?
  2. How software that runs wikipedia is tested
  3. How to spread CI to the team
  4. no session
  5. no session

11:15 Topics

  1. Continuous Interruptions
  2. Continuous Delivery with Puppet - what is missing?
  3. Stable end to end testing
  4. Continuous Integration with LARGE artifacts
  5. How to make devs care for production?

Lunch Topics

  1. Sprints are cool, but I find them a bit boring...

2:00 Topics

  1. Challenges in mobile automation and CI
  2. Integrating code reviews with CI
  3. ContinuousDeploymentWithoutCI
  4. What does the ideal look like?
  5. Spec by example war stories

3:15 Topics

  1. TDD Clinic
  2. Using git effectively with CI
  3. Monitoring Metries for user stalking
  4. Low level test code / library bleeding edge
  5. Future of testing Finding the right people

4:30 Topics

  1. Continuous Rewriting
  2. Multicomponent CI
  3.  ???
  4. Questions on the right level and amount of testing
  5.  ???


Table View

Room name 10:00 11:15 2:00 3:15 4:30
The Big Room Are we doing improvement wrong? Continuous Interruptions Challenges in mobile automation and CI TDD Clinic Continuous Rewriting
Meeting One How software that runs wikipedia is tested Continuous Delivery with Puppet - what is missing? Integrating code reviews with CI Using git effectively with CI Multicomponent CI
Library How to spread CI to the team Stable end to end testing ContinuousDeploymentWithoutCI Monitoring Metries for user stalking  ???
Meeting Two no session Continuous Integration with LARGE artifacts What does the ideal look like? Low level test code / library bleeding edge Questions on the right level and amount of testing
Garden no session How to make devs care for production? Spec by example war stories Future of testing Finding the right people  ???