The Latest
Lessons in Test Automation[magazine] 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[magazine] 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. |
Hung Nguyen
June 26, 2002 |
|
Designing Useful Metrics: Using Observation, Modeling, and Measurement to Make Decisions[magazine] First-order measurement can help you understand what's going on, make decisions, and improve results. Observation, modeling, and simple data gathering are things that you can implement in your work group without a big measurement program or big funding. Start by modeling your system and working out on paper how different measures will affect your system. Then involve your team, expand your model, and try some simple data gathering. This approach to measurement is one more tool in your toolkit, and it will move your organization toward better quality. |
||
The Influential Test Manager: How to Develop and Use Influence to Help Your Test Group - and Project - Succeed[magazine] 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. |
||
Software Installation Testing: How to Automate Tests for Smooth System Installation[magazine] Installation testing—especially manual testing—can sometimes be grueling. Here are several aspects of installation testing that are best suited to automated methods. |
Chris Agruss
June 26, 2002 |
|
On-Track Requirements: How to Evaluate Requirements for Testability[magazine] Prior to using the requirements to develop the Test Plan, an analysis should be performed to evaluate the testability of the requirements. This article suggests a proven method used on a recent project that accomplishes such an evaluation. |
Rodger Drabick
June 26, 2002 |
|
Cem Kaner on Rethinking Software Metrics[magazine] The theory underlying a measurement must take into account at least nine factors. This article defines these nine factors (e.g., the scope of the measurement, the scale of the instrument, and the variation of measurements made with the instrument) and applies them to a few examples. |
Cem Kaner
June 26, 2002 |
|
Avoiding Scalability Shock[magazine] 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. |
Billie Shea
June 26, 2002 |
|
Testing in the Dark[magazine] 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[magazine] 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. |
Mark Pawson
June 26, 2002 |
|
Karl Wiegers Describes Ten Requirements Traps to Avoid[magazine] Recognized requirements expert, Karl Wiegers, shares the symptoms and solutions for common requirements-related project problems, including inadequate customer involvement, vague and ambiguous requirements, inadequate change process, and scope creep. |
Karl E. Wiegers
June 26, 2002 |
|
Managing Your ERP Project[magazine] Managing your ERP Project |
Marie Benesh
June 26, 2002 |
|
Evaluating Tools[magazine] You, or perhaps your manager, have decided that it's time to choose a tool. Where do you begin? How do you go about comparing them? This article provides a five-step process for comparing, evaluating, and finally choosing the right tool for your organization. |
||
High Maturity Benefits and Blarney[presentation] With more and more organizations claiming to be Capability Maturity Model (CMM) Level four or five, is high maturity all it's cracked up to be? |
Bill Curtis, TeraQuest
|
|
Why Nobody in Our Business Can Estimate[presentation] To put it politely, software estimation has proven to be challenging. But to be frank, software estimation has proven to be a nightmare. |
Tim Lister, Atlantic Systems Guild, Inc.
|