|
That's No Reason to Automate! Automating test execution is supposed to give tremendous benefits, but often gives disappointing results—because it hasn’t met the objectives set for it. The fault may not lie with the automation itself, but with the objectives you are attempting to achieve. Aiming at the wrong target does not bring success! For example, objectives for automation are often confused with objectives for testing, but they should be different. In this article, learn how to avoid the most insidious traps and how to recognize good objectives for automation.
|
|
|
What to Expect When You're Automating Testing After learning the basics of testing frameworks, writing tests for your existing codebase can be a daunting challenge. Where should you start testing, and what kind of tests will be the most effective? Learn how to kick-start your testing and some solutions to problems teams frequently encounter.
|
|
|
Virtual Realities: Best Practices and Common Pitfalls of Adopting Virtual Lab Automation Virtual Lab Automation (VLA) is a ground-breaking technology that promises quantifiable benefits for application development and test organizations, including faster lab deployment, less manual setup work, greater resource flexibility and utilization, and easier reproduction of defects. In this article, Skytap's Ian Knox discusses the best practices and common pitfalls associated with adopting a VLA solution. In addition, he outlines the steps to evaluate a virtualization solution for your test organization and provides further resources to help you get started.
|
|
|
Off the Trails A focused approach toward testing a product is important, but sometimes we discover information that we didn't anticipate at all. One of the key skills in testing is dynamically managing our focus; sharpening it sometimes and widening it at other times. If we vary our approaches, we might find something surprising and broaden our coverage.
|
|
|
Taming the Headless Beast: A Proven Strategy for Testing Web Services The benefits of Web services are becoming widely demonstrated and accepted. However, these benefits are not without their own challenges. How can you enter data and verify the response of a system without a GUI? Are you ready to tame this headless beast?
|
|
|
A Map by Any Other Name A mapping illustrates a relationship between two things. In testing, a map might look like a road map, but it might also look like a list, a chart, a table, or a pile of stories. We can use any of these to help us think about test coverage.
|
|
|
The One-Hour Regression Test If a customer asked you to demonstrate to him, within an hour, that your newest software is ready for use, what tests would you run? Are these the same tests that you are now performing in your first hour of regression testing? They should be.
|
|
|
Got You Covered Excellent testing starts by questioning the mission. So, the first step when we are seeking to evaluate or enhance the quality of our test coverage is to determine for whom or what we're determining coverage.
|
|
|
It's a Bug! Bug triage, like labor and delivery triage, is about deciding a course of action on the spot, often with minimal information guiding decision making. Discover what other lessons Robert has learned from Anne's experience in nursing that have practical applications in his hunt for bugs.
|
|
|
Is There a Problem Here? Suppose you were testing an application that you had never seen before with no time to prepare, no specification, no documentation, no reference programs, no prepared test cases, no test plan, and no other person to talk to. How do you know that what you are seeing is a bug?
|
|