Productivity

This week there are several new solutions for scheduling issues in Test Studio 2013 R1, as well as some tweaks to old docs that may help you out. The new scheduling architecture is simpler and more reliable than ever before, but you can still run into some complications. In some scenarios—for example, if you delete a test project on disk before removing the scheduled test runs in the Results view—you might have scheduled test runs that you can't remove or edit. If you run into this issue, you can remove the scheduled test run on disk. Also, if you ...

JavaScript has a love-hate relationship with asynchronous code. The language loves to let you make asynchronous calls and developers start to hate JavaScript because its easy to create a giant mess. There are a lot of great patterns for handling asynchronous callbacks, of course. But it’s tempting to just hack some nested callbacks in place and end up with a giant monolithic sideways Christmas tree of doom doing that.

“Mocking” is one of those magical concepts derived from OOP that makes TDD possible. But as you saw in the last post, there are many different kind of mocks and each has its own strengths, weaknesses and purposes. We’ll discuss most of these types of mocks at some point in this series. But in this post I’m going to demonstrate one of the most common type of mocks you’ll use; the Stub.

We collect a lot of data during the testing process, but whether we put it to good use is a different story.  We run individual tests of test cases, and determine if they pass or fail.  If they fail, we determine at what point they fail, and provide the steps necessary to replicate that failure. We look for performance of individual transactions early on in the testing process, then when our goal turns toward deployment, we add virtual users to determine the behavior characteristics of the application and servers under stress, as well as whether it can successfully handle the ...

Our first live webinar about application analytics is scheduled for next Tuesday, and it will focus on .NET development. Our solution consultant Ramiro Milan will lead the conversation and will go over what EQATEC Application Analytics is, how it works, why it is important for developers, and how it can help you reduce support.