[CFP is CLOSED]
The theme for CAST 2015 is Moving Testing Forward.
The past ten years have seen dramatic changes in the nature of communications (the internet) and the nature of delivery, from PC to client/server to the web and web services. Deployment is different; monitoring is different, builds and test tooling are different. We have a variety of new models and methods for our testing. CAST is where we talk about how they actually work out in practice, based on experience.
The emphasis on “actually work out in practice” is by design and worth restating. We are less interested in hearing perfect practices everyone must do than in context – why the practice worked in a particular environment. We want to hear where you struggled, what you plan on doing next, and the kind of environments where you would /not/ recommend the practice.
These practices are not limited to testing or tooling, but can include social structures. New models and theories of testing are great — along with an example of how they played out on an actual project.
Roll up your sleeves and bring your retrospective notes.
At CAST 2015 speakers will be presenting stories, workshops and tutorials regarding their experiences surrounding how to advance software testing. Join us this summer for our tenth annual conference in downtown Grand Rapids, Michigan, August 3-5.
Call for Participation
We invite you to share your stories, thoughts, observations, and demonstrations surrounding your experiences about Moving Testing Forward.
We are seeking abstracts and proposals in line with the conference theme in these formats:
Track sessions include a presentation of up to 40 minutes, plus 20 minutes of moderated “open season” time, and include one conference pass. The best track session is probably an experience report from a real project. Presentations that present teaching material are also common. We will consider, but do not encourage panel discussions.
Interactive workshops of 2 hours are double-track sessions where the speaker will lead a discussion or conduct exercises. Our preference is for workshops that create concrete artifacts for participants to take home such as lists, mind maps. Workshops that involve actual doing of software testing will get preferential consideration. Please discuss the session, learning objectives, and deliverables created by students in the ‘additional information’ section of the proposal.
The theme is broadly set to provide a wide scope for submissions; however, we strongly encourage and prefer proposals based on your personal experiences.
A successful proposal will be sent as an attachment in the link below in a standard file format (MS Word or RTF, please no PDF). You do not need to be a member of AST to submit a proposal or to speak. A successful proposal will include:
Speaker name, email address, and phone number
Title and type of session (Track Session or Workshop)
Abstract – Roughly 150 words describing the material
Has this presentation been given at other conferences? Which one(s) and when?
An indication if you will write a paper for peer review (About papers.)
We encourage speakers to write a paper supporting their proposal. At submission time you need only indicate your willingness to write a paper. Drafts of the papers are not due until May 2nd, and final revisions by June 1, 2015. Note we do not require a paper, but we encourage it.
No more submissions accepted, the deadline for submission has passed.
Important CFP Dates
December 4, 2014 – Call for Proposals Open.
January 31, 2015 – Call for Proposals Close.
February 28, 2015 – Initial speaker selection will be complete.
Mid-March, 2015 – Speakers notified of selection & Provisional paper acceptance sent.
All deadlines change and/or expire at 11:59pm Eastern time.
A final word
We would like to humbly acknowledge the intense challenges involved in speaker selection. One obvious challenge is balancing known, experienced speakers while encouraging new and diverse voices and creating opportunities for development. Please send us your ideas on balance and speaker selection, using the email@example.com email address. Thank you!