Category: Testing

When was the last time you were on a website that was working fine, and all of a sudden, it seems to stop working? You click and all you get is the dreaded loading circle.

So you wait a couple more seconds, and nothing happens – the page is still loading. After a few more seconds of irritation, you finally get something…but it’s not what you hoped. Instead, you get a “Page Cannot Be Displayed” error!

Arrrrgggghhhh!!! You start screaming like Dr. Doofenshmirtz, cursing Perry the Platypus….Google it!

In the previous post, I talked about how having an application that was originally designed for the LAN is one reason why small and medium businesses need application testing. In you haven’t read it, go here.

In this post, I talk about reason #2.

So not only was this application also designed for users being local to the server, it was also deployed in a complex architecture of multiple tiers.

In part 2, I talked about how having an application that has multiple tiers is another reason why small and medium businesses need application testing. In you haven’t read it, go here.

In this post, I talk about reason #3.

When I was brought on to help resolve this application issue and started asking my questions, I found out that the issues the users were having occurred intermittently. Once I hear “intermittent”, I know I will need to do some continuous captures.

In part 3, I talked about how having an application being susceptible to intermittent issues is another reason why small and medium businesses need application testing. In you haven’t read it, go here.

In this post, I talk about reason #4.

In part 2, I mentioned that the customer was using NAT to separate its network from the SaaS provider’s network. That’s not uncommon. Every company wants to help protect its network from anything malicious from another network. Nothing new there.