Blog

The following article is a guest post by Scott Moore.

Performance is important to me – I think most of you know that about me and it would be an understatement. I am also one of those people who are never satisfied with just doing things half way. I feel that way about the work that I do for myself and the partners I work with.

In an effort to ensure that we follow the same advice that we give to clients, I decided to go through an exercise with one of our partner’s webmaster to look into performance of the en Read Entire Entry

It’s no secret that mobile applications, native, hybrid and web based, are in high consumer demand. The world is moving from the desktop to mobile devices. Tablets are projected to outsell PCs by Q3 2012 and mobile devices outshipped PCs in 2011. Mobile devices and tablets are the technology of the future. If your organization is not already invested in mobile applications, there’s a strong chance you will be in the near future.

Our clients asked us for solution recommendations and requirements to tackle the task of automat Read Entire Entry

This post will attempt to explain how VuGen SOAP calls look by comparing the WEB/HTTP protocol and the SOAP protocol. Below is an example of raw XML that is received from a request.
<?xml version=”1.0″ encoding=”UTF-8″?>
<soap-env:Envelope xmlns:soap-env=”http://schemas.xmlsoap.org/soap/envelope/”>
<soap-env:Header>
<Authentication soap-env:mustUnderstand=”1″>
<UserID>xxxx</UserID>
<Password>xxxx</Password>
</Authentication>
<Appl Read Entire Entry

We had a web application which was easy to script, but had an unusual situation dealing with the business rules that we had to work around. This was an application where users update their personal information, emergency contacts, and other forms.

The problem was the Emergency Contacts. Since this was a brand new application to the company, most users would not have anything listed and would need to input this information. The first time the user accesses the page, they would get a message that they are required to have at least on Read Entire Entry

Let’s discuss the “ResourceByteLimit ” option in web_url() function within VuGen. This attributes can help emulate a user that does not wait for a complete page to download before clicking on another URL. It is typically used for testing the availability of a site (as opposed to load testing a site) while minimizing network traffic.
Before each resource download, the script replay engine will check if the total download size is less than the ResourceByteLimit specified. If so, it will continue the download. Else, it will stop the Read Entire Entry

On my latest engagement, I needed a web script to go with all of the Citrix scripts I am creating. The web script was giving me some issues with correlation and NT authentication, so I decided to give Web Click and Script a try. I didn’t have much expectation since neither I nor my colleagues have been able to get it to work in the past, but I thought that it would be worth a try in 9.5. Imagine my surprise when it actually worked! This could partly be because the javascript is minimal. That seems to be where C&S hangs.

There i Read Entire Entry

Note: This article was originally posted on Loadtester.com, and has been migrated to the Northway web site to maintain the content online.
According to Robert B. Miller[1], here are acceptable response times for various actions:

One tenth of a second (0.1) is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.
One second (1.0) is about the limit for the user’s flow of thought to remain uninterrupted, even though Read Entire Entry