Company Size Doesn’t Impact the Need for QA Testing

testing-sign

As many of our readers know, we recently conducted a 2015 State of Selenium Survey. We were interested in the size of the companies each respondent represented, so we asked. Our audience was evenly distributed from companies with five or less employees to organizations with over a thousand.

The fact that companies of all sizes now recognize the importance of QA testing represents an important shift in not only software development but in customer relationship management. Think about the sheer number of products the public is exposed to on a daily basis. This has shifted the balance in power. Customers are now in control.

To compete, you need a great product that works. If, at release, your product is buggy and unreliable, you may not get another chance. Constantly testing the quality of your product demonstrates a level of respect for the end user that is appreciated and rewarded these days.Continue Reading

What SNL’s 40th can teach us about test management

header

This past Sunday, Saturday Night Live celebrated its 40th anniversary. 40 years! That’s insane. Why they didn’t celebrate it on a Saturday is equally insane, but I digress.

While I was enjoying the show (mostly on Hulu the next day) it dawned on me: are there any takeaways from this anniversary special that we can apply to the testing world?

You bet there are!

image1

1. Start with the essentials

I’m sure that a show that’s been around for 40 years had a difficult time trying to recap everything in one episode. So they did what we should do in the testing world: start with the essentials. What are the things that absolutely must be included?Continue Reading

Testers Do Not Break the Product

“Testers do not break the product.” Or do they?  I am not so sure this is true in all contexts.  One of the goals of testing is to understand the product quality.  To do that, we will need evidence and not just some gut feeling of the product’s capability.  To save on arguments, I will concede that any defect that is evoked is latent, dormant or resides in the product.  The flaw is in the product, either via definition (specification) and application (use) or execution via development process, and test personnel evoke that failure. They break the product.

Consider for example, embedded products.  Our organization will almost certainly have a multiple perspective approach to the testing of that product.  Multiple perspective in testing will consist of some exploratory and some combination of stimuli applied to the product.  One of those would be test the product to the requirements.  Testing to requirements are one means of learning the product’s ability to meet the expectations articulated via specifications.  The result of which should be part of the contract closure phase of the project.  Did we get what was specified?  This would be true whether external (supplier) or internally developed by our organization.  To close the project it is incumbent upon us to identify if the project expected outcome has been met.Continue Reading

Testing with a purpose

Picture this: you’ve just arrived at work, coffee in hand, ready to start the day. You know that you need to get some testing done and today is the day you’re going to find time to do it. So you respond to emails, move some meetings around, and voilà: you’ve just blocked off your afternoon so that you can finally do some uninterrupted testing. Perfect.

The morning whizzes by and before you know it it’s testing time. Nothing left to do but to do it. So you start your testing by meandering through your site, aimlessly clicking on things to see if they work, right?

Wrong!

“Aimlessly clicking” around your application is a waste of your time. You’ll quickly realize that the afternoon is over and you have little to show for it.

Why is that? You’re still testing, right? And as long as you’re testing you’re helping out the application somewhat, right?

Yes and no. Yes, every little bit of testing helps. But you can be far more effective if you go into testing with a purpose, rather than “aimlessly clicking” around.Continue Reading

Getting Started With Selenium

Often times in message boards we’ll see questions like “I want to start using Selenium, help!” or “I’m having trouble doing x, y, and z in Selenium, where do I go?!”

Fear not, my friends. There is a massive community of Selenium users just like yourself that are doing automated web testing and are willing to share their thoughts and experiences to help you get started.

So who are these people? Here’s where to look when you’re getting started with Selenium:Continue Reading