|
Guide Your Agile Development with Traceable Tests Testing professionals who are learning about agile often want to know how they can provide traceability among automated tests, features, and bugs and report on their testing progress. Here, Lisa Crispin gives an example of how her previous team worked together to integrate testing with coding and helped everyone see testing progress at a glance.
|
|
|
Redistributed Testing: A Shift to Refine Requirements In short, redistributed testing is a shift in the emphasis and responsibility for testing. Testers are reassigned to work closer to the business with users or business analysts or are embedded in the development team.By being involved in story and scenario writing, the testers help to refine requirements and improve their quality. How could your systems benefit from redistributed testing?
|
|
|
How Skeleton Strings Can Help Your Testing Brian Noggle writes about how he uses "skeleton strings" to help him when he probes an application under test. Just as skeleton keys unlock doors, these generic skeleton strings open up access to a wide variety of defects.
|
|
|
How to Test Your Website on Multiple Browsers: Four Solutions Compared Robbie Bridgewater writes on the difficulty in finding bugs during testing since no single computer can run all of the major browsers—not to mention the added challenge of testing various mobile operating systems. In this article, Robbie compares four possible solutions to this dilemma.
|
|
|
The Value of Really Dumb Tests When you start writing unit tests, the tests that seem useful might be too involved to give a quick payback. The ones you write quickly might seem too trivial to add value. By starting with small, seemingly simple tests, you can both overcome the inertia that stops you from testing and add value to your project.
|
|
|
A Word with the Wise: Assessment First with David Dang David Dang, a senior practice manager for Questcon Technologies, explains why you need think about the tool you select. According to Dang, the assessment of the project and its goals should always come first in test automation projects, otherwise, you risk maintainability issues down the road.
|
|
|
Not Your Father's Test Automation If you think that test automation is mostly about executing tests, then you're missing out on a big opportunity. Or rather, you're missing a lot of small opportunities adding up to a big one. Consider this: stop thinking about test automation as merely executing automated tests, stop thinking about test automation as something you need expensive tools for, and start discovering automation you can implement in a couple of days and usually with extremely inexpensive tools or tools you already have available. In this week's column, Danny Faught and James Bach suggest taking a more Agile approach to test automation.
|
|
|
Modeling Practice and Requirements Models are useful in different settings in different ways. Models can test facts, ideas and understanding, simulate operation, and aid coordination between systems and people. In this column, Becky Winant lists six model patterns she has seen in practice in software development organizations, talking about where each is appropriate, and the strengths and weaknesses of each.
|
|