You need to know what's on the cutting-edge of technology. Find out what's coming and the unique Warptest POV with just one click on the "Blog" tile.

All posts tagged Browsera

Testing Is Not Just For Amateurs…

… When is the last time you heard someone say,

“I know we’ll do the basic coding but get in someone with no experience to finish our disruptive app for us”?

Right. NEVER.

What Am I Doing Wrong?

Since you asked, here’s a short list to read, digest and nail with a riveting gun to your hiring manager’s table-top: –

Testing - 5 wrong things

So what do you do?

The Warptest POV

The value of Beta Testing is in taking the observations you receive and turning it into actionable intelligence for your Developers. Having a tester who adds these observations as bugs in your bug tracking and ensures they aren’t duplicates will make your life a lot easier.

Having a tester to plan and execute your testing in a professional manner will ensure a logical, efficient effort is made to provide optimal test coverage.

As for Cross Browser compatibility testing, I singled it out after reading yet another blog post about Best Cross Browser Testing Tools. Once again it’s Mashable writing an article that implies testing can be performed by any random bunch of dudes.

To their credit they incorporate two of my favorites BrowserStack and Browsera. Both are elegant in their simplicity if all you want to do is perform basic visual validation or in BrowserStack’s case add a layer of automation thanks to integration with Selenium Web Driver (an automation API to drive the browser natively).

BrowserStack supports 300 or so desktop and mobile browsers. Browsera makes it easy to test sites with logins, compare layouts and find scripting errors.

This slideshow requires JavaScript.

The big problem with all these blog posts on best tools … for Cross Browser compatibility is that they fail to explain the psychological impact of layout bugs on your users.

Content is king but if it’s displayed in a messy, visually irritating manner then you just lost the user who you forced to endure those bugs.

All because you didn’t understand the ramifications of not having these tests performed, or knowing which platforms / browsers / browser versions are your priority.

Isn’t this a laborious process? If planned and executed efficiently even by a manual tester then subject to the complexity of your site or app this shouldn’t be too time consuming.

So what have we learnt?

  • Don’t expect the same results from using amateurs as using professionals.
  • Use the right tools for the job.
  • Plan the work and work the plan.
  • Gareth Mallory says it best in the latest James Bond movie, Skyfall when addressing 007:

So what are you going to do to ensure your product’s success?