Conference Presentations

The Dirty Secret of Formal Software Testing

Arguably, James Bach has done some of the most rigorous testing that anyone has done in software testing-testing for court cases that are closely scrutinized by teams of lawyers. James once poured $250,000 of labor (nearly 400 hours) into a ten-minute test for a patent infringement case that was filmed for a jury. He also has tested a Class III medical device subject to FDA audit. In all his testing, James has noticed something important that no one mentions when talking about formal testing. It seems to be a secret, a dirty secret: All good formal testing is based on informal testing. Yet you don't see this admitted in any of the "textbooks" or "maturity models" or "testing standards." Join James as he tells you exactly why informal testing must be the basis of formal testing and, as a special bonus, explains why so many people pretend that formal testing stands by itself.

James Bach, Satisfice, Inc.
Moving to the Next Level: From Tester to Visionary Manager

Would you like to chart a better course for your test team but don’t know where to begin? Before you can plan for a better future and take your team to the next level, you first must know where you are. George Viegas has developed a quick and easy checklist you can use to evaluate the testing function in your organization. The checklist identifies more than thirty items in major areas such as test automation, team maturity, and process. For example, the team maturity area identifies whether a team is in regression test mode only or actually has the capacity to perform performance and load testing. This checklist is a powerful tool not only to analyze your team but also to establish forward looking goals and the plans for achieving them. Take back tools to help you move beyond just managing test-start managing the plan for your team’s future.

George Viegas, Thomson Reuters
Surviving or Thriving: Top Ten Lessons for a Professional Tester

As testers and test managers we often find ourselves struggling to survive within our organization-sometimes with the possibility of outsourcing or offshoring just around the corner. We often are asked to become more “effective” and more “efficient” with time and resources-to do “more with less.” However, most testers and test managers are unsure of what this actually means. Lloyd Roden shares ten valuable and practical lessons on how you can actually become better at what you do in testing and thrive in your career. Lloyd’s lessons include using modern technology, reviewing test documentation, testing the testers with techniques such as "bug seeding", reporting project waste, providing management with feedback on decisions that they made, and more. This session will be challenging and practical for all testers, test leads, and test managers.

Lloyd Roden, Lloyd Roden Consultancy
Simple and Informative Performance Tests You Can Do Now

When most people think of performance testing, they think about the hard-or the very, very hard-parts, those expensive and complicated tools that simulate the activity of thousands of end-users while collecting tens or hundreds of thousands of measurements. Scott Barber tells those looking to start performance testing to start with easy and mid-level tests. While it is true that accurately simulating high-activity production usage is difficult and expensive, you can detect and diagnose many performance issues with the tools and knowledge you have at your disposal right now. In fact, much of the performance information needed by stakeholders to make good decisions and by developers to dramatically improve performance is easily obtained by performance-testing novices.

Scott Barber, PerfTestPlus, Inc.
STAREAST 2012: Session-based Exploratory Testing on Agile Projects

One of the challenges associated with testing in agile projects is selecting test techniques that “fit” the dynamic nature of agile practices. How much functional and non-functional testing should you do? What is the appropriate mix of unit, integration, regression, and system testing? And how do you balance these decisions in an environment that fosters continuous change and shifting priorities? Bob Galen has discovered that session-based exploratory testing (SBET) thrives in agile projects and supports risk-based testing throughout the development project. SBET excels at handling dynamic change while also finding the more significant technical- and business value-impacting defects. Join in and learn how to leverage SBET for test design and as a general purpose agile testing technique.

Bob Galen, iContact Corp
Test Automation in a Mixed Software/Firmware Environment

Test automation is an attractive choice for dealing with regression testing, high-volume repetitive testing, data-driven testing, and high risk software that needs its tests to be strictly repeatable. However, the automation tools on the market focus on either software or firmware, so they only offer solutions to pieces of the puzzle. Through a case study from Boston Scientific’s Neuromodulation division (BSN), Christopher Crapo shares the benefits and pitfalls of building an in-house test automation system combining off-the-shelf software components and custom tools. Learn how BSN created a scriptable interface to support simultaneous UI, database, and embedded testing and how that interface fit into their overall testing approach.

Christopher Crapo, Boston Scientific
Security Testing: The Foundations and More

Your organization is doing well with functional, usability, and performance testing. However, you know that software security is a key part of your assurance and compliance strategy for protecting applications and critical data. Left undiscovered, security-related defects can wreak havoc in a system when malicious invaders attack. If you don’t know where to start with security testing and don’t know what you are looking for, this session is for you. Alan Crouch describes how to get started with security testing, introducing foundational security testing concepts and showing you how to apply those security testing concepts with free and commercial tools and resources. Offering a practical risk-based approach, Alan discusses why security testing is important, how to use security risk information to improve your test strategy, and how to add security testing into your software development lifecycle.

Alan Crouch, Coveros, Inc.
Test Management for Cloud Applications

The "cloud" can deliver services over the Internet in three flavors-software as a service (SaaS), platform as a service (PaaS), and infrastructure as a service (IaaS). Testing cloud services requires test managers to focus on more than classical functional testing to address additional risks-new Internet dependencies, different security challenges, and performance concerns-brought by the cloud. Ruud Teunissen shares the still-growing list of new concerns and risks with cloud services and explores ways to mitigate them with test-related actions. When selecting a cloud service provider and architecture, services must be tested against business and technical requirements. Prior to production, you can employ end-to-end regression tests to confirm that the cloud service operates as expected. Join Ruud and learn to identify specific requirements, risks, and test strategies for your company to migrate application to the cloud.

Ruud Teunissen, Polteq Test Services B.V.
Software Testing in the Cloud: Issues and Opportunities

Cloud computing offers virtualized hardware, unlimited storage, and built-in software services that can aid in reducing the execution time of large test suites. However, migrating software testing to the cloud is not a trivial activity nor is it necessarily the best solution to all testing problems. Using real-world case studies conducted at the Florida Institute of Technology, Scott Tilley describes the issues and opportunities of software testing in the cloud. He explains how the SMART-T decision framework they use can support your migration process. Scott shows how to realize significant time savings using HadoopUnit, a cloud-based distributed environment for concurrent execution of test cases, which builds upon the Hadoop open-source platform. Leave with a better understanding of when cloud computing is a solution to your software testing problems and when it's not.

Scott Tilley, Florida Institute of Technology
STAREAST 2012: The Tester's Role in Agile Planning

If testers sit passively through agile planning, important testing activities will be missed or glossed over. Testing late in the sprint becomes a bottleneck, quickly diminishing the advantages of agile development. However, testers can actively advocate for customers’ concerns while helping the team implement robust solutions. Rob Sabourin shows how testers contribute to the estimation, task definition, clarification, and the scoping work required to implement user stories. Testers apply their elicitation skills to understand what users need, collecting great examples that explore typical, alternate, and error scenarios. Rob shares many examples of how agile stories can be broken into a variety of test-related tasks for implementing infrastructure, data, non-functional attributes, privacy, security, robustness, exploration, regression, and business rules.

Rob Sabourin, AmiBug.com

Pages

CMCrossroads is a TechWell community.

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