This year marks the third Eclipse Testing Day. The event is organised by BREDEX GmbH and the Eclipse Foundation and will take place over the course of one day. The focus is on testing with, for and at Eclipse.

Registration and payment

You can register for the event using this website. Credit card payments are accepted. If you prefer to pay via invoice, please send a formal purchase order to:

testingday@bredex.de
or by fax to +49-531-243-3099

Please state that the purchase order is for the Eclipse Testing Day, the names and companies of the participants, and specify whether your company is a member of the Eclipse Foundation or not. Once we receive the purchase order, you will receive a code with which you can register your participants without having to enter credit card details.

Agenda

Panel discussion

This year, the program committee want to improve the interaction possiblities for participants. To get everyone talking and learning from each other, we've organised a panel of experts to answer questions on the the topic of "asymmetric testing". We are pleased to welcome our panel members:

• Michaela Greiler, TU Delft
• Dr. Frank Simon, SQS AG
• Jana Knopp (geb. Hoffmann), Xing

Asymmetric testing: Leveraging the power of the community

One of the particularities of open source software is the stark difference between the amount of users compared to the amount of developers / team members. For a development team with only a handful of core members, uncountable users in the community are acting as testers – putting the software through its paces for standard and less-common use cases, updating to new versions, working in different environments. Each community member can enter bug reports, patches and enhancement requests.

The size difference between the development team and the user community leads to the concept of asymmetric testing. In a thriving community such as the Eclipse community, the relative sizes of project teams to users can be staggering.

What are the effects of asymmetric testing on the software process? What benefits or disadvantages does it have? What can non-open-source projects learn from this type of testing to improve their quality? What could open source projects do better to improve their testing and user experience?

The Eclipse Testing Day Program Committee has put together a panel of speakers from different areas of testing expertise. Over the course of the discussion, the audience has the chance to ask questions about testing and listen to answers from these various perspectives. The aim of the discussions is to learn more about the factors influencing testing and to find out how to choose suitable strategies for individual projects.

Topics for discussion include:

• Continuous / frequent delivery vs. long delivery cycles
• Agile vs. traditional testing - Open testing (community, betas) vs. closed testing
• Certification vs. experience
• Automatic vs. manual testing
• Scripted vs. exploratory testing
• Separate test team vs. integrated testers
• Safety critical testing vs. business application testing
• To beta test or not to beta test

We’re looking forward to a lively discussion! If you have questions that you would like our moderator to ask, then contact the team using the address below.You will also be able to add your questions during registration.

You can see a list of warm-up questions prepared by the program committee on the talks page on the wiki.

Sponsors and supporting organizations

The Eclipse Testing Day is a not-for-profit event, and is made possible by our sponsors and supporting organizations.