MOIIST is a Software Testing peer conference. MOIIST stands for MOntreal Insights Into Software Testing. MOIIST is facilitated in the style of LAWST workshops. Presentations are based on the first-person experience of invited delegates.
MOIIST accepts French or English language submissions and presentations.
MOIIST 2015 CALL FOR PROPOSALS (CFP)
The Content Owner, Nimesh Patel, along with the MOIIST Organizers – Robert Sabourin and Stephanie Ripeau, invite you to submit your proposal for MOIIST 2015.
MOIIST 2015 THEME
The theme of this yearʼs workshop is Test Reporting.
Experienced software testers and development professionals are invited to share experience reports about test reporting.
Reporting the results of Testing is often one of the most valuable deliverables of any testing effort to project stakeholders. The notion of test reporting is answering questions from stakeholders to help them make informed decisions. This workshop will explore how testers interact with different project stakeholders in order to report the results of their testing effort. Who do testers report testing information to? What do testers actually include in their test reports? How do testers report the outcome of testing? When do testers report test results? How do test reports vary due to lifecycle, business, technology, organization and cultural factors?
We are seeking a wide variety of test reporting stories. We would like to share examples of great successes and dismal failures. What worked? What did not work? Did test reporting impact stakeholderʼs decision to go ahead, or to not go ahead with a system under test?
By sharing test reporting stories, we hope to identify specific skills which could be taught and shared to foster better communication of test efforts. After each experience report is shared, a short affinity analysis will be done to capture relevant test reporting skill ideas.
Test reporting skills are especially important for testers working on projects where stakeholders and decision makers depend on and require testers to provide and communicate good, up to date, and clear information on the results of the test effort. How testers communicate and present the actual story about the testing effort to stakeholders and what stakeholders believe they need to know about the testing effort in order to make decisions based on quality related information from testers can at times be quite tricky. How can we teach testers to communicate and report the results of testing effectively to stakeholders in a manner in which the stakeholders receive the information they expect while also providing them with valuable and accurate information about the testing that was done.
Short summaries of presented test reporting stories will be collected and made available to the testing community.
Some examples of test reporting stories could include:
- Good reporting
- Bad reporting
- Ineffective reporting
- What works
- What doesnʼt work
- Reporting the testing story
- Reporting only numbers and counts
- Status reporting
- Coverage reporting
- Individual tester communicating their results
- Test team communicating their results
- Test reporting to help stakeholders advance on KPIʼs
- Fancy reporting not telling the whole story
- Test reports generated by tools
- The notion of metrics in test reporting
About Experience Reports
Experience Reports describe an experience that you had firsthand. You will tell your story as a narrative, with (or without) any visual aids you feel might help you explain the situation (architecture diagrams, graphs, etc). Then, you will answer questions about what happened, and the group will discuss issues brought to mind from hearing your story. The goal is not to present tools, methodology, or practice, but to share what you saw and did in your work. Both positive and negative outcomes are instructional.
More guidance on experience reports can be found here: www.moiist.org. You can also learn more about Experience Reports by watching a video on the subject here: http://www.youtube.com/user/WOPRWorkshop.
Conference Location and Key Dates
Saturday, January 17, 2015: 9:00 AM to 5:00 PM
Sunday, January 18, 2015: 2:00 PM to 6:00 PM
The conference will be held in the downtown Montreal area.
MOIIST is a peer workshop for practitioners to share experiences in software testing, to allow people interested in these topics to network with their peers, and to help build a community of professionals with common interests. Our constituency is people who are interested in all areas of software testing.
MOIIST is not vendor, consultant, or end-user-centric, but strives to provide a mix of viewpoints and experiences. The range of potential interest is broad, from single-device embedded systems to complex ecosystems that are multi-tier, multi-platform, and multivendor, including components spread across multiple organizations.
To learn more about MOIIST, visit www.moiist.org.
No fees are charged to participate in MOIIST.
Delegates will be selected from applicants by MOIIST organizers with an attempt to get a broad variety of experiences from different business, organizational and technical contexts. A maximum of twenty delegates will be invited from among applicants.
Please send proposals to: email@example.com
Submissions should include a short summary of the proposed experience report (max. 500 words) along with a short summary of the candidatesʼ relevant experience. The deadline for receiving submissions is November 22, 2014. Successful applicants will be informed by December 1, 2014.