Resources

Recently, we worked on a high-risk, high-visibility system where performance testing ("Let's just make sure it handles the load") was the last item on the agenda. As luck would have it, the system didn't handle the load, and very long days and nights ensued. Why it does have to be this way... Read this article about Risk Mitigation to ensure this doesn’t happen to you.

Continue reading →

Recently, we worked on a high-risk, high-visibility system where performance testing (“Let’s just make sure it handles the load”) was the last item on the agenda. As luck would have it, the system didn’t handle the load, and very long days and nights ensued. Delivery was late, several serious disasters were narrowly averted, and large costs were incurred.

Continue reading →

The Testing performed by our Test Group is Black Box Testing. This paper will discuss the following areas of our test effort in more detail:

• Client-server GUI testing
• CTI client-server testing
• IVR applications testing using simulated calls
• Product-wide integration testing using multi-tools (CallSim, Fake -Pipe, QA Partner) Approach · Management considerations

Continue reading →

This is an excerpt from my book, Expert Test Manager, written with James Rommens and Leo van der Aalst. I hope it helps you think more clearly about the test strategies you use.

A test policy contains the mission and objectives of testing along with metrics and goals associated with the effectiveness, efficiency, and satisfaction with which we achieve those objectives. In short, the policy defines why we test. While it might also include some high-level description of the fundamental test process, in general the test policy does not talk about how we test.

The document that describes how we test is the test strategy. In the test strategy, the test group explains how the test policy will be implemented. This document should be a general description that spans multiple projects. While the test strategy can describe how testing is done for all projects, organizations might choose to have separate documents for various types of projects. For example, an organization might have a sequential lifecycle test strategy, an Agile test strategy, and a maintenance test strategy.

Continue reading →

Performance testing is easy, right?  Grab a tool, record a transaction with the server, ramp up a thousand virtual users...  What do you often get?  A hot mess!  Performance testing is likely the kind of testing most likely to be done poorly.  It does not have to be that way.  Join us to learn what performance testing is not: not easy, not guaranteed, but not impossible to do well.  Much of a good performance testing program is not about using the tool at all; instead it includes all of the ISTQB buzzwords: static testing, early testing, planning and preparation.  Learn the basics of successful performance testing and improve your performance test project.

Listen now →