Conference Presentations

Testing the New Disney World Website
Slideshow

At Walt Disney Parks and Resorts Technology, we provide the applications and infrastructure our online guests use to plan, book, explore, and enjoy their stay at our parks and resorts. With millions of page views per day and a multi-billion dollar ecommerce booking engine, we face a unique...

Les Honniball, Walt Disney Parks and Resorts Technology
Building Quality In: Adopting the Tester’s Mindset
Slideshow

When trying to improve the development process, agile and lean transformations often start by focusing on engineering. Product management and development get a lot of attention; however, tester is not one of the defined Scrum roles. Despite the attention given to automated tests...

Stephen Vance, Stellar Advances
STARCANADA 2014: Security Testing Mobile Applications
Slideshow

Due to the sensitive nature of the personal information often stored on mobile phones, security testing is vital when building mobile applications. Jeff Payne discusses some of the...

Jeff Payne, Coveros, Inc.
Test Automation—It’s a Journey, Not a Project
Slideshow

Organizations implement automated testing in hopes of reducing time and cost while creating higher quality products. They invest in tools, training, and development; identify candidates...

Paul Maddison, The CUMIS Group
Courage and Freedom in Exploratory Testing

Exploratory testing (ET) consists of simultaneous learning, test design, test execution, and optimization. Most people are able to adopt the outward behaviors of ET but struggle to adopt an ET mindset. Griffin Jones explains that this mindset requires reflecting on four basic questions...

Griffin Jones, Congruent Compliance
Using Mindmaps to Develop a Test Strategy
Slideshow

Your test strategy is the design behind your plan—the set of big-picture ideas that embodies the overarching direction of your test effort. It captures the stakeholders’ values that will inspire, influence, and ultimately drive your testing.

Fiona Charles, Quality Intelligence
STAREAST 2013: Maybe We Don’t Have to Test It
Slideshow

Testers are taught they are responsible for all testing. Some even say “It’s not tested until I run the product myself.” Eric Jacobson believes this old school way of thinking can hurt a tester’s reputation and—even worse—may threaten the team’s success. Learning to recognize...

Eric Jacobson, Turner Broadcasting
Mobile Testing Methodologies: Trends, Successes, and Pitfalls
Slideshow

In today's dynamic mobile marketplace—where new handsets and mobile operating systems are released every day—your ability to deal with these changes which impact your mobile product is vital. The mobile application lifecycle today must be short; must be of great quality; cover...

Eran Kinsbruner
Specification-by-Example: A Cucumber Implementation
Slideshow

We've all been there. You work incredibly hard to develop a feature and design tests based on written requirements. You build a detailed test plan that aligns the tests with the software and the documented business needs. When you put the tests to the software, it all falls apart because the requirements were updated without informing everyone. But help is at hand. Enter business-driven development and Cucumber, a tool for running automated acceptance tests. Join Mary Thorn as she explores the nuances of Cucumber and shows you how to implement specification-by-example, behavior-driven development, and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber bridges the communication gap between business stakeholders and implementation teams.

Mary Thorn, Deutsche Bank
Back to the Basics: Principles for Constructing Quality Software
Slideshow

Using an analogy to the building codes followed by architects and contractors in the construction of buildings, Rick Spiewak explores the fundamental principles for developing and delivering high quality, mission-critical systems. Just as buildings are constructed using different materials and techniques, we use a variety of languages, methodologies, and tools to develop software. Although there is no formal "building code" for software, software projects should consider-and judiciously apply-the recognized "best" practices of static analysis, automated unit testing, code re-use, and peer reviews. Rick takes you on a deep dive into each of these techniques where you'll learn about their advantages, disadvantages, costs, challenges, and more.

Rick Spiewak, The MITRE Corporation

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.