Hot Software and Performance Testing Links – Week of April 18th

softwaretestinglinks1 Hot Software and Performance Testing Links   Week of April 18th

This week in software and performance testing

A few Observations on structure in testing
Over the years, it’s been common for people in our community to mention exploratory testing, only to have someone reply, “Oh, so that’s like unstructured testing, right?” That’s a little like someone refer to a cadenza or a musical solo as “unstructured music”; to improv theatre as “unstructured theatre”; to hiking without a map or a precise schedule as  “unstructured walking”; to all forms of education outside of a school as “unstructured learning”. When someone says “Exploratory testing is  unstructured,” I immediately hear, “I have a very limited view of what ‘structure’ means.”

Scale Fail
Hilarious video from Josh Berkus at MySqlConf 2011

What is Facebook’s architecture
Quick summary of Facebook’s architecture

uTest partners with Mozilla to build a test case management system
Test Case Management can be trickier than herding cats.  If you work for a small to mid-sized company and everyone’s counting on you to QA the apps to glowing perfection (no pressure, right?), then you’ve clearly demonstrated you’re a supremely organized person.  It’s in your DNA.

Selecting the right CDN for your website
A Content Delivery Network (CDN) shortens that distance between your static content and the end-user.  While the text on most web pages is dynamic, most images, JavaScript, and CSS are static.  These static objects make up a large percentage of the total bytes downloaded for each page view.  By using a CDN, you place static content as close to the end-user as possible.  In turn this decreases the page load time a end-user experiences by leaps and bounds.

Some technical details on IBM’s Watson
IBM Watson’s stellar performance in the Jeopardy! show captured the world’s imagination. The first real world application for Watson involves healthcare. How does Watson address issues that previous generations of tools have not been able to address?

The black team
The computing world was different in the 1960′s. Computers were massive, expensive, and required full-time staff just to keep them running. Product cycles were scheduled in years not months. Tasks modern programming tools do in seconds took weeks. And whenever a new computer model was developed, the operating system and all applications had to be developed from scratch.

What is testing?
I think it’s easy to blur the line between what testing is, and what testers do. I’m not convinced it’s correct to blur the line (or incorrect for that matter), but I do think it’s a frequent cause of confusion among testers

Can your programming language do this?
One day, you’re browsing through your code, and you notice two big blocks that look almost exactly the same. In fact, they’re exactly the same, except that one block refers to “Spaghetti” and one block refers to “Chocolate Moose.”

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>