Posted in exploratory testing, mobile testing, production bug, tools

(Live) slow connection mobile testing

(s)lowconnection (2)

Holidays are these times when we go outside, fly abroad, spend a lot of time on wasting it and basically doing nothing. What is a common feature of such places?
Slow internet connection – no matter if it is within your network or WiFi.
I, an addicted smartphone user, find it as a one of the most annoying things EVER!

As I probably wrote at least once, I use my smartphone (Android) as a mother ship 😀
(It would really be a pain if I lost it).
Anyways, I use my phone for shopping purposes as well. What is more, taking into account a ‘typical woman‘ stereotype – I do a lot of shopping. 90% of which I do online. The conclusion is simple – the more time I have to waste – the more I buy 🙂 Having said that, imagine my frustration during online shops explorations, when I do experience slow internet connection.
In addition, I am not talking about websites only, but about well-known native apps, which , as it turned out, are not supposed to handle limited network range.

Today, I would like to present you a true wall of glory, basing on my holidays explorations. I’ve called it – the SlowCo Art Gallery of inspiring issues.
Don’t get me wrong, I don’t want it to be pure hate only, but maybe an inspiring feature to test for all of you working with any kind of mobile application or websites.

How to handle such testing (to avoid irritating me in the future)? Short introduction down below or in one of my old posts here.

Shall we begin?

Pic.1. Where is my CSS? – Example from


Pic.2. A journey through classes? – Example from H&M Android app


Pic.3. We don’t know what the hell just happened, so we’ll provide you with a random message – Example from native Twitter app
Translation from Polish: An important service, without which this application is not able to run, is currently not available. Try later.)


Pic.4. We are creative in producing 404 pages – Example from website


Pic.5. At least one of those messages is valid. Hopefully. – Example from Google Play app


As you can see – the range of failure possibilities is really vast BUT the issue is the same in each example. In the end, all those bugs may seem funny 🙂

On the other hand, we are able to protect our applications and websites against SHAME by performing sets of basic network connection test cases.

How to stress the app, pretending slow connection?
My favorite option is to open Chrome, click F12 on your computer and go to Chrome Developer Tools.
Navigate to Network -> Throttling and select a connection version that you are interested in. Slow your connection down, and see the magic 🙂
You can also connect your mobile app with Chrome Dev Tools and stress it.


It may sometimes seem as an edge case, but imagine all the people, who live most of their lives in the area of slow internet connection. How frustrating might it be for them?
Hey mobile testers – Let’s make apps great again! 🙂

Like!, Share, Hate, Comment on Facebook
Stalk me on Twitter
or comment down below 🙂


Posted in exploratory testing

Cat testing – why not?



Monkey testing

The term ‘monkey testing’ is rather known in tester’s world. It is a technique where a user tests the application or system by providing random inputs. We believe that unorganized test inputs are able to brake the application in the way that a trained tester won’t even try. It is basically true, because people tend to repeat known moves and actions. Pesticide paradox warns testers that they should change and update their test scripts often, otherwise they’ll stop finding issues. From this point of view – acting as a monkey seems to be tempting especially within the area of regression testing – not as a replacement but rather as the appendix to standard test suites.

Cat testing

On the other hand, animal kingdom is way bigger than just an ape type. If a monkey can test – why a cat can’t?

Today is a World Cat Day so this blog post would be related to my buddy – Greebo.

I am a cat-lover and I spend some part of each day observing my cat playing around with stuff. Trying to better my approach to exploratory testing, I just started thinking – isn’t my cat a great example of such tester?

A cat has any knowledge about things they play with. But they play anyway. This is what exploratory testers are supposed to do.
Exploratory way of testing fits to any kind of testing methodology, any type of company and project. You don’t have to be experienced in any subject (as ISTQB would like you to think), because it’s not the point. The most important aim is to play with application and to achieve a purpose.


Exploratory testing might be dedicated to UI, functions or potential safety risks check. It may help to find out if the software is prone to malicious attacks as well as if it is easy to access for a novice user. Context  is the key to success.

Cat checks random features of stuff so hard in order to know them or to brake them, just like exploratory testers do. Cat does a lot of damage in certain sessions in order to provide fun for himself among naps and snacks.


Purpose is important. Cats have their own purposes of running around and attacking things. Exploratory testers should also have some certain purpose of testing and don’t stop before an exploratory session is finished.


Time frame is essential. When you start exploratory session – you can’t stop. Did you see a cat, who digs in a pot with flower when no one watches  and having brakes for pee? NO WAY. He digs so hard until the destruction is complete and then runs away pretending it wasn’t him. That would be a proper session of exploratory testing description. You specify the time frame, start and fight. You can finish only when you run out of your time.

One major thing that is different between a cat and an exploratory tester is that the cats cannot provide any notes 🙂 Note taking is an essential part of exploratory testing.

On the other hand, cats leave so much mess behind that in most cases you know exactly what they just did. Wondering HOW might take a while. That is also a good hint for you – if you hate taking notes – record what you do using for example Chrome DevTools or other apps. In the end it would be easier to recall what you’ve just did.

I would like to encourage you to level up your daily test routine and try to enrich test sessions in cat-like exploratory testing and just have more fun in what you do. Enjoy!