The Latest
Using Test Automation Frameworks[presentation] As you embark on implementing or improving automation within your testing process, you'll want to avoid the "Just Do It" attitude some have taken. |
![]() |
|
Patterns of Testability[presentation] Testability requires interfaces for observing and controlling software, either built into the software itself or provided by the software ecosystem. |
Alan Myrvold, Microsoft
|
|
The Myths of Rigor[presentation] We hear that more rigor means good testing and, conversely, that less rigor means bad testing. |
![]() |
|
Lessons Learned from 20,000 Testers on the Open Source Mozilla Project[presentation] Open source community-based software development can be extremely wild and woolly. Testing in this environment is even more so, given that it is often less structured than software design and coding activities. |
Tim Riley, Mozilla
|
|
The Buccaneer Tester: Winning Your Reputation[presentation] Who drives your career as a tester or test leader? Hopefully, not the company for which you work. It's you-you must be the driver. |
![]() |
|
Stop Guessing About How Customers Use Your Software[presentation] What features of your software do customers use the most? What parts of the software do they find frustrating or completely useless? Wouldn't you like to target these critical areas in your testing? |
![]() |
|
Agile Testing: Uncertainty, Risk, and How It All Works[presentation] Teams that succeed with agile methods reliably deliver releasable software at frequent intervals and at a sustainable pace. At the same time, they can readily adapt to the changing needs and requirements of the business. |
![]() |
|
You Can't Test Quality into Your Systems[presentation] Many organizations refer to their test teams and testers as QA departments and QA engineers. |
![]() |
|
![]() |
Amplifying Collaboration with Guerilla Facilitation[article] Sometimes, an ineffective meeting can be more damaging than no meeting at all. But, if you're not the person in charge of facilitating the meeting, how can you help keep the group and the meeting in line? In this article, Ellen Gottesdiener offers some suggestions for both facilitators and non-facilitators that may help ease some of your meeting frustrations. |
|
We're All in the Same Boat[article] Lisa Crispin dives into the "we're all in the same boat" theory and explains how it can't be more true in the software development world. From the need for common goals to going beyond taking responsibility for the team's actions, each team must know that you're going to fail or succeed together. |
||
Unconscious Limitations to Your Testing[article] This article examines the limitations to testing efforts that testers unconsciously apply. Limitations such as premature conclusions, assumptions, biases and industry norms can all cut the thinking process short. Suggestions will be offered on how to identify when you are limiting your testing and how to challenge yourself to keep your mind actively thinking. |
Lynn McKee
May 20, 2010 |
|
Motivation Visibility, and Unit Testing[article] Steve Berczuk has always been interested in organizational patterns and recently found himself thinking about motivation. Agile practices, both technical and organizational, build a framework which makes having the right amount of collaboration and feedback possible. But there's a bootstrapping process: How do you get people to start doing the practices, especially technical ones, such as unit testing? |
||
Lean and Agile Practices Have Their Roots in the Quality Revolution[article] Reading and reflecting upon lean and agile this month I realized that technology professionals do not realize how many of these practices are actually from the quality revolution that was led by luminaries including Shewart, Juran, Crosby and Deming. The Poppendiecks have certainly done a great job not only with sharing their lean practices, but also reminding us that process improvement has been successfully implemented in many settings long before it was applied to software development. Join me as we take a quick look back at where the journey to quality began! |
||
Why Agile Development Requires Agile Configuration Management[article] In his CM: The Next Generation Series, Joe Farah writes that anyone who thinks that agile development implies minimal CM is probably in the situation of not having to deal with customers. Instead, agile development requires agile CM; configuration management tuned to the agile development shop and philosophy. |
||
Adapting the Agile Mindset to Software Configuration Management[article] With the advent of agile in the mainstream, it raises awareness of the challenges in getting software configuration management functionality established that suits the working processes of Agile methods. While not necessarily new to some software configuration management professionals, the primary challenge is how to adapt CM practices in a tangible way that supports Agile values while not discarding the CM values that ensure integrity of the product under development. |