I was giving a demo to a partner last week using SOASTA CloudTest Lite and I had included some monitoring in the demo. People on the call who are doing performance/load testing using open-source products were very impressed by our ability to setup monitoring for any kind of infrastructure while being able to combine and correlate the infrastructure performance counters with the application performance data. And everything in real-time! So I though I would record a quick video to show everyone how it’s done. If you’re interested, you can find more than 50 in-depth CloudTest Lite videos on our CloudLink website.
I’ll be flying out to London next week and participate to 2 testing events.
First, I will meet our new partner Testhouse and hold a joint webinar: Load and Performance Testing in Today’s Web and Mobile World – A revolution with SOASTA CloudTest. This is an introduction to cloud testing where I’ll have an opportunity to share some of the good stuff we’re doing with SOASTA. If you’re into load and performance testing, you’ll quickly realize that there is no turning back: Testing from the Cloud is your best choice today if you truly care about the performance of your web or mobile application. I love games (big chess fan, not very good though. Ping me if you want to play on redhotpawn.com) and there will be a game with a very nice prize for the winner. I can’t tell you more …
On Friday, I will participate to the SIGIST Conference and yes, I will talk about … Cloud Testing. Hopefully, my talk will lead to some very interesting discussions! While I love webinar, face-to-face discussion are the best! Conference topics will range from test automation, agile testing, test requirements and of course performance testing! I can’t wait to hear Mieke Gevers talk: Ever been fooled by performance testing results. I can definitely relate to the topic and it should lead to a good discussion. The complete agenda for the conference is here [PDF]
Before talking about why I’m so excited today, let me tell you a story. 18 months ago, as I was investigating SOASTA CloudTest for my own Software Testing organization, I had a chance to get a demo from Dan Bartow and a chat with Tom Lounibos about the product. Slavy Slavov who was heading our team in Sofia, Bulgaria was also part of the call. We were litteraly blown away by what we were seeing! My organization was using HP Loadrunner at the time (and you should know what I think about LoadRunner …) and CloudTest seemed way ahead of the competition: Leveraging public and private clouds, real-time analytics, a very innovative visual approach to test creation and execution etc. Slavy and myself were sold on first sight! Beside features and technical questions, I’ve asked the rather obvious question about an evaluation version of CloudTest, something my team could play around for a while before making any purchasing decision. Myself couldn’t wait to have a chance to play with it! Well, to my upmost disapointment there was no trial version available. Tom offered a proof-of-concept for whatever projects we were working on but the timing was too tight for us. We left it at that unfortunately …
Next week, I am heading to Rome to present at the International SOA Conference – Moving SOA into the Cloud. I’ll be giving the presentation I gave at DataCenter 2011, but with additional content. Of course there will be some specifics about how to approach testing SOA in the Cloud but also content on the type of problems cloud testing allows to find across all environments we usually test in ie. Lab, staging and production environment via real customers’ story.
For example, how easy it is for a badly designed page to cap out your bandwidth (yes, we’re at 238mbits/s!) and max out your webservers with a low volume test in a staging environment.
How a fix in a load balancer firmware can help you go from this (horrible) situation ie. 6% error rate, response rate to the roof after 15min, bandwidth capping out.
To this much better situation ie. 0.001% error rate (can’t get better than that!) with 172K virtual users.
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
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.
Real World Performance and the stir trek web site The site opened for registration a few weeks ago and sold out very quickly. However, there were some issues with the web site that were troubling. The site basically died under the load – obviously not a great first impression. Fortunately the dev community is pretty awesome in Ohio, and after the initial spike in traffic when the “doors” opened for ticket sales, the site seemed to work fine. However, there was the nagging fear that it would have similar issues on the day of the event, which would of course be bad.
Website downtime survival guive Let’s be honest. Website downtime can infuriate us. And according to some, downtime can do much worse. It can affect user confidence, loyalty and ultimately eat into your bottom line. How can we dodge the fail whale? While we answer it, we might also engage in a bit of swashbuckling. Arrr!
TDD Doesn’t guarantee defect-free code TDD, for example, does not remove the need for testing. We flesh out our algorithms and OO designs using – ideally – a minimum list of examples that describes the overall behaviour. once we’ve reached the example that leads us to the general solution, all nicely refactored on the inside, then as far as TDD is concerned we are done.
Vendor sues HP over Web testing software
A California software vendor is claiming that Hewlett-Packard officials evaluated its eValid website testing technology, then subsequently stole its intellectual property for use in a rival product released last year, according to a complaint filed in U.S. District Court for the Northern District of California.
The HP booth staff (Goons) owe me an apology – Old post from @adamgoucher I’ve discovered this week I’m pretty pissed that those two from the HP booth had the nerve to try to censor me. The proper thing they should have done is to ask to talk to me and see if they could try to address my concerns about their product. They’re not going to win me as a convert, but at least they would know what I was saying and the reasons for it. But instead they sent down the goon squad.
Testing for the Cloud Making the rounds of test-related conferences this past year, I’ve noticed that—because our industry isn’t immune to hype—cloud computing and how to test it has started to be a talking point. One conference organizer came right out and said they wanted a couple of talks on the subject for their next event. And if it is a looked-for conference topic then you just know that mainstream testers are going to think they need to pay attention.