The Australasian testing community has another reason to rejoice. We welcome the 1st issue of Testing Trapeze Magaine! Katrina has done a wonderful (and often hard) job of pulling together a fantastic magazine. And two of our own HTW writers, Aaron and David, are in it with cool articles that I am sure will rock some boats. So take some time over the weekend to have a look and read and I’m sure you will not be disappointed. And if you have something to say get in contact with Katrina to get published in future releases.
Tag Archives: usability
Web Page Analysis Basics for Testers
I usually move in the performance testing realm and one of the things I regularly do, is check for obvious omissions in website design before I get into the low down with testing.
What do I mean by that?
There is such a thing as (and I am having difficulty writing this) Best Practice, when it comes to web page development. These are technological imperatives that can be easily checked by using simple tools. You don’t need to be an HTML guru to use these or to gain more knowledge about your website under test.
Performance Ideas from 1-Click-Buy
Why do we performance test?
*duh* because we want faster response times…. oh and we want to know how to scale our virtual machines…. oh and we want to tune our systems… oh and XXXXX…. there are tons of reasons. Performance testing has it’s testing rigor and we go and “hammer” the system to get at those answers.
One thing I like to do (because it’s fast and cheap) is use a calculator/spreadsheet for performance testing. I take architecture diagrams of present and future systems, infrastructure diagrams, requirements, human oracles and more and put all the numbers together. Then I check if they stack up. Like where the product tries to get 1GB of data across a 10Mbit network link in under a second. I don’t need a test to be able to tell you, that there’s a problem there.
But then it struck me today. There is something similarly simple that I am not doing (and am guessing not many performance testers do)….
Ask yourself, what is the web page that has a response time of 0.000 milliseconds and has a infinitesimally small throughput footprint?