Conference Presentations

It's Too Darn Big: Test Techniques for Gigantic Systems

Structuring test designs and prioritizing your test effort for large and complex software systems are daunting tasks, ones that have beaten many, very good test engineers. If you add concurrency issues and a distributed system architecture to the mix, some would simply throw up their hands. At Microsoft, where Keith Stobie plies his trade, that is not an option. Keith and others have reengineered their testing, employing dependency analysis for test design, model property static checking, "all pairs" configuration testing, robust unit testing, and more. They employ coverage to successfully help select and prioritize tests and make effective use of random testing including fuzz testing security. Finally, models of their systems help them generate good stochastic tests and act as test oracles for automation.

  • Test checklists for large, complex, distributed systems
Keith Stobie, Microsoft Corporation
Do You Want Fries With That Test?

Connect with an expert to learn how to work smarter and learn new ways to uncover more defects. In this issue, Michael Bolton dishes out commentary on why testers who master skills instead of memorizing techniques are relished in the software industry.

Michael Bolton's picture Michael Bolton
The Expert as Impediment

Turn to The Last Word, where software professionals who care about quality give you their opinions on hot topics. This month, Brian Marick offers advice on why people are sometimes right to resist experts.

Brian Marick
Injecting Testability into Your Test Designs

The term dependency injection has attained buzzword status within the programming community. Follow Agile developer J.B. Rainsberger as he goes beyond the buzz and breaks down a specific example of how injecting a dependency can improve the testability of your design.

J.B. Rainsberger
Grow Your Test Harness Naturally

Spring is in the air. It’s the time of year when plants wake from their winter dormancy and start growing out of control. Kind of like building a test harness. Take a tip from the Agile field this season and build your harness one test at a time. No fertilizer required.

Kevin Lawrence
Combined Strengths

One school of thought says each should do what he's best at and no more. But one company has graduated to a new way of life. Instead of isolating testers and business analysts, the two teams are melded into one—resulting in a more robust product created in less time at a reduced cost. Could this hybrid approach work for you?

TechWell Contributor's picture TechWell Contributor
Testing Without a Map

When faced with the task of testing an unfamiliar application, it's sometimes difficult to know where to begin. Discover how exploring with heuristics in mind can help you uncover bugs—even when you don't know what the system specifications are.

Michael Bolton's picture Michael Bolton
Using Personas to Improve Testing

Too often testers are thrown into the testing process without direct knowledge of the customers' behaviors and business process. As a tester, you need to think and act like a customer to make sure the software does-in an easy-to-use way-what the customer expects. By defining personas and using them to model the way real customers will use the software, you can have the complete customer view in designing test cases. Get the basics of how to implement customer personas, their limitations, and ways to create tests using them. See examples of good bugs found using personas while learning to write bug reports based on them.

  • What you need to know to develop customer personas
  • Use customer personas for designing test cases
  • The types of bugs found by using personas but missed by other techniques
Robyn Edgar, Microsoft
STARWEST 2004: Testing Dialogues - Technical Issues

Is there an important technical test issue bothering you? Or, as a test engineer, are you looking for some career advice? If so, join Esther Derby and Elisabeth Hendrickson, experienced facilitators, for "Testing Dialogues - Technical Issues." Practice the power of group problem solving and develop novel approaches to solving your big problem. This double session takes on technical issues, such as automation challenges, model-based testing, testing immature technologies, open source test tools, testing Web services, and career development. You name it! You will share your expertise and experiences, learn from the challenges and successes of others, and generate new topics in real-time. Discussions are structured in a framework so that the participants will receive a summary of their work product after the conference.

Facilitated by Esther Derby and Elisabeth Hendrickson
The Four Schools of Software Testing

Testing experts often disagree. Why? Different testers have different understandings of the role and mission of software testing. This session presents four schools of software testing, each with a different understanding of the purpose and foundation of testing. One school sees testing based on mathematics. Another sees it as an activity that needs to be planned and managed. A third sees it as a basis for understanding and improving software process. And the fourth sees it as an intelligence service, providing actionable information. These all sound reasonable enough, but each has provided the foundation for a school of testing and different hierarchies of values. Learn more about the four schools of software testing and the effects they have on your life. You may find that you, your colleagues, and management are operating in different schools.

Bret Pettichord, ThoughtWorks

Pages

CMCrossroads is a TechWell community.

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