Web or eBusiness Testing

Tutorials

TJ Exploring Usability Testing for Mobile and Web Technologies SOLD OUT

Rob Sabourin, AmiBug.com

Tue, 10/14/2014 - 8:30am

It’s not enough to verify that software conforms to requirements by passing established acceptance tests. Successful software products engage, entertain, and support the users' experience. Goals vary from project to project, but no matter how robust and reliable your software is, if your users do not embrace it, business can slip from your hands. Rob Sabourin shares how to elicit effective usability requirements with techniques such as storyboarding and task analysis.

Concurrent Sessions

W14 Testing the New Disney World Website

Les Honniball, Walt Disney Parks and Resorts Technology

Wed, 10/15/2014 - 3:00pm

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 set of challenges. Join Les Honniball for insights into how they work with Product Owners and development teams to design tests, both manual and automated for these challenges.

W15 End-to-End Test Automation with Open Source Technologies

Ramandeep Singh, QA InfoTech

Wed, 10/15/2014 - 3:00pm

As organizations continue to adopt agile methodologies, testers are getting involved earlier in product testing. They need tools that empower them to manage varied test automation needs for web services, web APIs, and web and mobile applications. Open source solutions are available in abundance. However, most of these solutions are independent and not integrated, significantly increasing the tester’s work around test automation development. Ongoing test automation suite evolution and building a robust regression test suite have become cumbersome.

T9 Automation Abstractions: Page Objects and Beyond

Alan Richardson, Compendium Developments

Thu, 10/16/2014 - 11:15am

When you start writing automation for your projects, you quickly realize that you need to organize and design the code. You will write far more than “test” code; you also will write abstraction code because you want to make tests easier to read and maintain. But how do you design all this code? How do you organize and structure it? Should you use a domain specific language? Should you go keyword driven or use Gherkin? Should you use page objects with POJO or Factories? Do you create DOM level abstractions? Where do domain models fit in?