Difference between revisions of "CITCONANZ2013Sessions"
From CitconWiki
Jump to navigationJump to searchWardGushee (talk | contribs) |
WardGushee (talk | contribs) |
||
Line 41: | Line 41: | ||
# placeholder | # placeholder | ||
# placeholder | # placeholder | ||
− | # [[PerformanceTestingInAgile]] | + | # [[http://www.citconf.com/wiki/index.php?title=CITCONANZ2013Session/PerformanceTestingInAgile]] |
# placeholder | # placeholder | ||
Revision as of 21:10, 10 February 2013
CITCON ANZ 2013 Sydney Sessions
Back to the Main Page
10:00 Topics
- placeholder
- placeholder
- placeholder
- placeholder
11:15 Topics
- placeholder
- placeholder
- NoMeansNo
- placeholder
- placeholder
2:00 Topics
- placeholder
- placeholder
- placeholder
- placeholder
- placeholder
3:15 Topics
- placeholder
- placeholder
- placeholder
- placeholder
- placeholder
4:30 Topics
- placeholder
- placeholder
- placeholder
- placeholder
- [[1]]
- placeholder
Table View
# | 10:00 | 11:15 | 2:00 | 3:15 | 4:30 |
---|---|---|---|---|---|
Hall of Justice | Problems adopting Continuous Delivery | Challenges in writing maintainable acceptance tests | Jeff is angry at silo thinking and DevOps isn't helping | Automated Testing of Automated Tests | Coding Dojos |
TV Lounge | DevOps and Testing | placeholder for 11:15 am | Testing Lightening Talks | ATDD in action - Live demo of automated acceptance testing | BDD from requirements to acceptance tests / Specification by Example |
Lunch Corner | Testing using robots | No means No - how to keep test failures meaningful | Distributed automated testing for 300,000+ unit tests | Catharsis | How to get started with Continuous Delivery, especially for small teams |
Ping Pong Table | Proxy Product Owner | Scaling up CD - Case study from telecommunications | Ask a vendor anything - Jenkins and Bamboo | Challenges of testing and deploying at scale | More time for coffee - 5 (soft) steps to CD |
Pool Table | placeholder for 10 am | Testing vs Checking | Discussion on increasing automation - how best to deal with legacy code | Selenium Best Practices | Performance Testing within an agile methodology |