Productivity

This week we have lots of new load testing content in the Test Studio documentation. To help you use Test Studio's load testing features to their full potential, we have created three new knowledge base articles on designing your load tests. The Load Testing Strategies article describes four of the most common load test types, and how to start designing them in Test Studio. Our Selecting Load Traffic page describes some general principles to use in choosing the user profile traffic to capture or import into your Test Studio load test. And in the Profiling Your Application KB article, ...

The last couple posts have seen us using basic Stubs to mock out the functionality a class that our code under test is dependent on. We focused on dealing with an external resource and being able to replicate enough of that resources functionality to satisfy our test. In this post I’ll introduce a new, simple test case. Over this and the next post you’ll see that not all “simple” test cases are so simple.

I mentioned in my last post on project data and analytics that testers and other project professionals certainly use data generated through various tools in helping us determine application quality, our progress to schedule, and to track defects, for example.  But the organization of the data and our inability to ask the right questions prevents us from deeply understanding our software. Why is it so important that we understand our data beyond a few graphs and charts?  The reason is that many projects fail altogether and are cancelled.  Many more don’t achieve all of their important objectives.  One of the ...

In the last post I introduced you to Stubs and wrote a simple example that returned a canned value for a method based on a parameter. In this short post I’ll show you another feature of stubs that can help ensure that your subbed method is be called correctly.

Despite trying to achieve simplicity, Agile teams may still run across difficult issues. In this section some of the more common challenges are explored. HANDLING INCOMPLETE WORK AT THE END OF AN ITERATION It is not uncommon for a team to have incomplete work at the end of an iteration. Unfinished work is an important issue to identify as it signals a potential problem with one or more aspects of the team. When an iteration is planned, the team sets an expectation with the customer. When those expectations are not met, the customer could lose faith in the team’s ability ...