Here’s some help on how to get through a common interview question. How to test a… well anything.
Such questions are asked to test your curiosity and approach to testing. They may sound stupid, but will hopefully reveal how a tester thinks and works.
This post will help you figure out how to test a toaster or any other random household appliance (yay!).
What is a Test Automation Framework?
A test automation framework is an application that allows you to write a series of test without worrying about the constraints of the underlying test tools.
It’s a set of protocols, rules, standards and guidelines that can be followed as a whole so you can leverage the benefits of the scaffolding provided by the framework.
They’re rules, standards and guidelines to make the life of your test team more enjoyable.
An automation framework is not a tool to perform a specific task, but rather an infrastructure that provides the solution where different tools can do their job in a unified manner. It’s an Automation Engineers common platform.
There are multiple Layers Of An Automation Framework. The part we are talking about now holds everything together. When someone says they help build automated test (like myself) they’re normally talking about this middle layer.
I was working at a place where we had thousands of test cases in our database.
This wasn’t a problem until we realized that many of the test cases where dead.
By dead I mean they were completely absolute at the worst or just redundant at the best.
This initial build up happened slowly, and before we knew it we where waste deep in old scripts.
Of course we always said we would go through and clean things up. When we started working on it though something else more important would come up.
We where able to slow the progress but we never truly reversed it.
The chilling reality is most, old test cases never die. I’ve seen test cases turn with my own eyes. They can cluster, and disrupt test development.
I’m here to tell you that zombie test cases are real. Don’t be afraid, this post will hopefully help you survive a zombie test case outbreak.
This is the second post on the different types of software testing. The first 20 types of software test can be found here.
I’m listing these testing types because a common interview question is ‘What types of testing would you do on a chair?’.
This should be used as a reference or quick reminder. The goal isn’t to memorize everything in this list.
I’ve seen some pretty bad test cases in my day.
Just to be fare I’m sure I’ve had a bunch of letdowns myself.
Alright maybe it was just once… yea one horrible test case. That sounds about right.
But seriously, if you work at a software company you’ve probably seen at least one poorly written test case.
If not well todays you’re lucky day.
Have you ever noticed how a few testers seem to get more done effortlessly?
Everything about them is comfortable, confident, & nonchalant yet deliberate at the same time.
What is it about these individuals that sets them apart?
I’ve written bug reports in the past that suck… No that REALLY suck.
From spares one liners to the long epics. I’ve done it all.
Thankfully now I know better.