The Latest
![]() |
Changing the Testing Conversation from Cost to Value[presentation]
Slideshow
The software testing business is in the grip of a commoditization trend in which enterprises routinely flip flop between vendors—vendors who are engaged in a race to the bottom on price. |
![]() |
![]() |
Collaboration without Chaos[presentation]
Slideshow
Sometimes software testers overvalue the adherence to the collective wisdom embodied in organizational processes and the mechanical execution of tasks. Overly directive procedures work—to a point—projecting an impression of firm, clear control. But do they generate test results that... |
![]() |
![]() |
Cause-Effect Graphing: Rigorous Test Case Design[presentation]
Slideshow
A tester’s toolbox today contains a number of test case design techniques—classification trees, pairwise testing, design of experiments-based methods, and combinatorial testing. Each of these methods is supported by automated tools. |
![]() |
![]() |
Bad Testing Metrics—and What To Do About Them[presentation]
Slideshow
Many organizations use software testing metrics extensively to determine the status of their projects and whether or not their products are ready to ship. Unfortunately most, if not all, of the metrics in use are so flawed that they are not only useless but possibly dangerous—misleading... |
![]() |
![]() |
The Role of Emotion in Testing[presentation]
Slideshow
Software testing is a highly technical, logical, rational effort. There's no place for squishy emotional stuff here. Not among professional testers. Or is there? Because of commitment, risk, schedule, and money, emotions can run high in software development and testing. It is easy to... |
![]() |
![]() |
Driving Down Requirements Defects: A Tester’s Dream Come True[presentation] The industry knows that a majority of software defects have their root cause in poor requirements. So how can testers help improve requirements? Richard Bender asserts that requirements quality significantly improves when testers systematically validate the requirements as they are developed. |
![]() |
![]() |
Build Your Own Performance Test Lab in the Cloud[presentation]
Slideshow
Many cloud-based performance and load testing tools claim to offer “cost-effective, flexible, pay-as-you-go pricing.” However, the reality is often neither cost-effective nor flexible. With many vendors, you will be charged whether or not you use the time (not cost effective), and... |
![]() |
![]() |
Integrating Canadian Accessibility Requirements into Your Projects[presentation]
Slideshow
In 2014, most Canadian businesses will face significant challenges as government regulations go into effect, requiring websites to be accessible to users with disabilities. Are your project teams knowledgeable about the technical accessibility standards? |
|
![]() |
It Seemed a Good Idea at the Time: Intelligent Mistakes in Test Automation[presentation]
Slideshow
Some test automation ideas seem very sensible at first glance but contain pitfalls and problems that can and should be avoided. Dot Graham describes five of these “intelligent mistakes”—1. Automated tests will find more bugs quicker. (Automation doesn’t find bugs, tests do.) ... |
![]() |
![]() |
Presenting Test Results with Clarity and Confidence[presentation]
Slideshow
Test leaders are often asked to present the results of their testing to management—and even to auditors. Can you clearly and confidently explain and summarize your test plans and results? Can you prove that your testing is compliant with internal procedures and regulations? |
![]() |
![]() |
Testing—After You’ve Finished Testing[presentation]
Slideshow
Stakeholders always want to release when they think we’ve finished testing. They believe we have discovered “all of the important problems” and “verified all of the fixes”—and now it’s time to reap the rewards. However, as testers we still can assist in improving software by learning about... |
![]() |
![]() |
Setting Automation Expectations: Lessons from Failure and Success[presentation]
Slideshow
Test automation is undeniably a key strategy for any test manager—and for good Test automation is undeniably a key strategy for any test manager—and for good reason. Test automation promises faster regression testing, higher productivity, better quality, and cost reduction. |
![]() |
![]() |
Yin and Yang: Metrics within Agile and Traditional Lifecycles[presentation]
Slideshow
Metrics are powerful tools when used to effect positive change in a project or organization. However, the value and benefits of metrics are often dependent on the context. While certain metrics provide information and insight to drive decision making for a traditional development approach... |
![]() |
![]() |
Baking In Quality: The Evolving Role of the Agile Tester[presentation]
Slideshow
While more and more organizations are practicing agile development methodologies, many have not learned how to “bake in quality” throughout the process. As an agile tester, you are an integral part of the development team—working on requirements, design, implementation... |
|
![]() |
Strength in Numbers: Using Web Analytics to Drive Test Requirements[presentation]
Slideshow
Once a client’s website is built, you’d think it would be time for a well-deserved break. However, almost immediately, questions come up—can we capture a larger audience? close more orders? increase our sales? And so, it’s time to redesign the site—and the test strategy and plans... |
![]() |