In this keynote presentation from the Better Software Conference & EXPO, Jean Tabaka proposes three pivotal practices that we must embrace to aggressively attack waste in software delivery—software-as-a-service, community, and fast-feature throughput.
Elisabeth Hendrickson spent several years on a quest to discover how testers can contribute effectively on extreme programming projects. In this STAREAST keynote presentation, she shares her experiences and lessons learned about how testers can play well and succeed on XP teams.
Whether we develop software-based systems to create invoices, solve difficult physics problems, diagnose heart disease, or launch rockets, we've learned that nothing stays the same very long and software defects are inevitable. However, one thing has remained constant: The role and value of testing has been misunderstood by many in senior management. A Lockheed Martin Fellow since 2005, Tom Wissink describes steps undertaken at Lockheed Martin to change this culture of misunderstanding into a culture of appreciation, satisfaction, and excitement.
In this keynote presentation by Bharat Mediratta and Antoine Picard, learn the story of Google's Testing on the Toilet's. This started from a deceptively simple idea to a company-wide cultural phenomenon that has received national acclaim.
Grab some hot cocoa, sit back, and watch this software tester's take on A Christmas Carol by the Grove Players.
Lee Copeland is concerned with things that the testing community is forgetting. In this video, he explains the "Nine Forgettings," the negative effects of each, and how recognizing them can help us improve our testing, our organizations, and ourselves.
Math is often not easy to learn, even for those of us who enjoy it. And if you don't use your mathematical knowledge, you just might forget how to use it. Danny Faught likes math and has found ways of using basic math like algebra, the modulo function, expected values, and logarithms in testing. It's kept his mind fresh on mathematical concepts and formulas, and he hopes it will do the same for you. In this week's column, he explains how to use math to improve testing.
Each week, I find myself using Jenga, Hasbro's wooden building block game, as an analogy for introducing agile into the enterprise. Few topics are more hotly debated throughout the software development community than how to apply the simple values of agile to big business. Many approaches favor knocking down the entire Jenga tower to start from scratch with an entirely new foundation of values and practices. Others opt for the comfort of traditional management processes, with some agile practices — like pair programming and stand-up meetings — sprinkled on top.
Exploratory testing--questioning and learning about the product as you design and execute tests rather than slavishly following predefined scripts--makes sense for many projects. But does it make sense for agile projects? In this week's column, Johanna Rothman examines how exploratory testing might work on an agile project.
In automated customer testing, scripts can operate with system under test (SUT) objects indirectly, via some interfaces: graphical user interface (GUI), application programming interface (API), command-line, etc. Business objects may contain a number of data fields. If many of these fields are supposed to be used in some data or behavior verification, the problem of business data storing can appear. This article describes general approach for complex business objects testing.
Recommended Web Seminars
Agile Connection is one of the growing communities of the TechWell network.
|Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery. Join the conversation now!|