The Latest
|
A Deeper Dive Into Dashboards[presentation] This session is a deeper examination of how to apply dashboards in software testing.I spent several months on a project primarily building a software testing dashboard. I have learned some interesting things, including: |
Randy Rice, Rice Consulting Services
|
|
|
The Many Hats of a Tester[presentation] As testers, we must wear many hats to do our job effectively. |
Adam Goucher, Zerofootprint
|
|
|
STAREAST 2010: Testing AJAX: What Does It Take?[presentation] Using AJAX technologies, Web 2.0 applications execute much of the application functionality directly in the browser. While creating a richer user-experience, these technologies pose significant new challenges for testers. |
Joachim Herschmann, Borland (a Micro Focus company)
|
|
|
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. |
Andrew Pollner, ALP International Corp
|
|
|
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. |
James Bach, Satisfice, Inc.
|
|
|
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. |
James Bach, Satisfice, Inc.
|
|
|
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? |
.jpg?itok=Wj3vQjhs)
Alan Page, Microsoft
|
|
|
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. |
Elisabeth Hendrickson, Quality Tree Software, Inc.
|
|
|
You Can't Test Quality into Your Systems[presentation] Many organizations refer to their test teams and testers as QA departments and QA engineers. |
Jeffery Payne, Coveros, Inc.
|
|
 |
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. |
||
|
Agile Tips and Advice - Index Cards - Wave of the Past, Present and Future[article]
Podcast
In a podcast that will surely get you thinking, we take a look at why the index card, yes, the simple index card could be the most valuable project management tool of all time. Take a listen and see if you agree that you simply cannot live without them on an agile project. |
||
|
Transitioning to Agile Testing[article] Your developers are already working feature-by-feature in iterations, but your testers are stuck with manual tests. How do you make the leap to agile testing when the nature of agile's iterative releases challenges testers to test working segments of a product instead of the complete package? In this column, Johanna Rothman explains that the key challenge resides in bringing the whole team together to work towards the completion of an iteration. Only then will the testers—and the entire team—know how to transition to agile. |
Pages
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.