What Is Exploratory Testing and Why It Is Great (Aka ET 101)

I’m pretty sure you have heard things about Exploratory Testing, you have most probably heard about how awesome it is. (Yes! This is the secret weapon!) And you may think you know it ALL. You are doing it, your team is doing it, so all should be good, according to the big book of plans you are all covered.

When you say or hear that someone was finding bugs by “just clicking around and found these issues, I did some exploratory testing“, then you can be as certain as death and taxes that it was not exploratory testing.

When you hear from the scrum master/whoever that “let’s do some exploratory testing before the live release just to make sure that everything is fine“, then you can be certain that they have no idea what they are talking about.

So what’s the point of Exploratory Testing? WHY is it great?

There is a psychological background. Let me explain.

Continue reading What Is Exploratory Testing and Why It Is Great (Aka ET 101)

Advertisements

Oh, Those Lovely Interviews

I have been browsing through the recent job postings for different QA roles lately, and I realized that there is only one thing in which these postings differ from each other – and this is the stack listed. And maybe the company description which tells us how great that company is, like they have bean bag chairs, table tennis, video games, etc.

I understand that it is not easy to write a job ad that stands out, from which I could predict that ‘yes, these people really know what they are looking for in a candidate.’

Nevertheless, one applies. What can go wrong? One might ask.

Well, a lot!

Continue reading Oh, Those Lovely Interviews

The Two Sides of Crowd-Sourced Testing

I was a huge fan of crowd-sourced testing.

I joined a smaller crowdsource testing company as a tester 9 years ago. I fell in love with the idea to have projects tested by a crowd with different backgrounds, experiences, and skills.

I immediately saw the advantages of crowd-sourced testing for companies:

  • valuable feedback to the development about the product within one or two days
  • a great diversity of devices and software versions
  • reveal bandwidth issues based on location and real network providers
  • localization testing by native speakers
  • low testing costs

and I saw the advantages of crowd-source testing for testers:

  • individual growth in different domains
  • learn about new testing tools
  • learn by example: reading others’ bug report is a great inspiration

Continue reading The Two Sides of Crowd-Sourced Testing

UI Is the Reflection of the Overall Product Quality

UI issues. A misaligned element, a typo or a not localized piece of text in a supported language. In some organizations testers have access to code and are allowed to fix issues, thus they can fix typos right away as soon as they encounter with one. But this is not the case for every company that can have many reasons. In this latter case, the tester files an issue and sets its priority. Because UI issues are usually classified as low priority issues in the global context, it can stay in the bottom of the backlog for a long time.

Here’s a roleplay for you.

Continue reading UI Is the Reflection of the Overall Product Quality

My Recap of WeAreDevs ’18

WeAreDevelopers Congress was happening in a few months back, in May, in the wonderful city of Vienna.  I held back writing a sum up about my learning because I was waiting for the recordings to be public so that I could link my top picks. And I missed a couple of talks I was interested in, so I wanted to catch up on what I missed at that time. Sometimes it was really hard to choose which talk to join as there are lots of sessions in parallel, and in some cases, there was a high demand for some talks so that no more people were allowed to go into the rooms.

The list of my favourite talks:

Continue reading My Recap of WeAreDevs ’18

Oh, Marionette, My Dear

When I was running a UI test locally I encountered this in the log file:

[exec] INFO: Retrying request to {}->http://localhost:14804
[exec] Jul 30, 2018 10:17:34 AM org.apache.http.impl.execchain.RetryExec execute
[exec] INFO: I/O exception (java.net.BindException) caught when processing request to {}->http://localhost:14804: Address already in use: connect

Sometimes even the was hung and the browser was closed after a while. So basically I couldn’t execute a single UI test locally that frustrated me.

I will say a few words about the environment I work with. “There is no use saving it until later.” (To use the words of  Richard Brautigan’s words, which is a favorite sentence of mine from ‘In Watermelon Sugar’.)

The test framework I work with is based on top of Selenium Webdriver, it is an extra layer – please don’t ask why. The implementation of this framework is done by another team. Details are overspread, so a lot of digging required if I want something to know.

Spoiler alert!
This framework is launching Firefox 52 by default.

Continue reading Oh, Marionette, My Dear