|
Perspectives from a Test Manager: Four Keys to Keeping Your Testing on Track This article highlights four keys to getting better organized: 1. A common set of ground rules on the test progress, defect reporting, and verification; 2. The ability to convey how your team’s testing is going--on a frequent basis; 3. Knowing what needs to be tested--and being able to stand behind the reasons why; 4. Maintaining good communication with the development leaders to help move the product through the development phases--being proactive rather than reactive.
|
|
|
Step-By-Step Test Design Testers are often faced with short development cycles and partial product specifications. This simple, six-step design method helps you come up with a reasonably thorough set of tests for individual product features in a reasonable amount of time. It employs list and table and encourages you to look at the software from a variety of perspectives.
|
|
|
Session-Based Test Management: A Strategy for Structuring Exploratory Testing Unlike traditional scripted testing, exploratory testing is an ad hoc process. Everything we do is optimized to find bugs fast, so we continually adjust our plans to refocus on the most promising risk areas; we follow hunches; we minimize the time spent on documentation. That leaves us with some problems. For one thing, keeping track of each tester’s progress can be like herding snakes into a burlap bag. Every day I need to know what we tested, what we found, and what our priorities are for further testing.
|
|
|
The Influential Test Manager: How to Develop and Use Influence to Help Your Test Group - and Project - Succeed Test managers often feel that while somebody might be in control of schedules or resources, they certainly are not. An experienced test manager shares ways to develop and use professional influence to help the test group.
|
|
|
Lessons in Test Automation Elfriede Dustin has worked on many projects at various companies where automated testing tools were introduced to a test program lifecycle for the first time. In reviewing these projects, she has accumulated a list of "Automated Testing Lessons Learned," taken from actual experiences and test engineer feedback. In this article, she will share examples of this feedback, hoping that this information will help you avoid some typical false starts and roadblocks.
|
|
|
Testing Web-based Applications To be most effective in analyzing and reproducing errors in a Web environment, you need to have a command over the operating environment. You also need to understand how environment-specific variables may affect your ability to replicate errors. With the application of some of the skills covered in this article, your Web testing experience should be less frustrating and more enjoyable.
|
|
|
Software Installation Testing: How to Automate Tests for Smooth System Installation Installation testing—especially manual testing—can sometimes be grueling. Here are several aspects of installation testing that are best suited to automated methods.
|
|
|
Avoiding Scalability Shock Web application scalability tops the list of challenges for those designing and developing e-commerce sites. Here are five steps to managing the performance of e-business applications: architecture validation, performance benchmarking, performance regression testing, performance tuning and acceptance, and continuous performance monitoring.
|
|
|
Testing in the Dark How can you test software without knowing what it should do? Here is a step-by-step approach to overcoming undocumented requirements, including how to discover the requirements, how to define "quality" for the project, and how to create a test plan including release criteria.
|
|
|
The Test Matrix: How to Keep a Complex Test Project on Track When testing needs to account for different user environments and installation configurations, the possible combinations can add up quickly. Read how one company used a simple data organization method to keep everything on track.
|
|