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.
Wildbit has shared their Good/Bad essays on different company roles. The definition given for QA Engineer is so good that I thought I would share.
A good QA engineer takes full accountability for the quality of each product release. They put quality ahead of everything, even if it means having candid conversations with team members. They are willing to delay a feature release in order to uphold product quality…
A bad QA engineer views themselves as a separate resource to blame developers for crappy code. They see value in the number of issues found, rather than the importance or impact the issue has on the product. A good QA engineer is a partner to the developer, with a mutual mission of having the most painless release possible.
The original blog post that goes into the inspiration for these essays can be found on the Wildbit blog here.
You can find the full document on Good QA Engineer | Bad QA Engineer is great! You should definitely give it a read.
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?
Was looking through Quora, and saw a great answer to this question What are the characteristics of a bad software engineer?
It got me thinking about what makes a bad software developer in test.
Here’s the list in my experience.