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 douglas.pl

Screenshot_2017-08-12-14-24-30

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

Screenshot_2017-08-16-09-15-07

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.)

Screenshot_2017-08-15-21-02-44

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

Screenshot_2017-08-11-11-00-31

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

screenshot_2016-08-12-23-11-04

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.

throttling

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 🙂

Cheers!

Advertisements
Posted in tools

How does the Internet work? #Balsamiq

hope-you-have-an1

Two at once blog post.

#1 Balsamiq

Balsamiq is an amazing tool for UI prototyping. Any of you could take advantage of it. It helps not only in UI prototyping, but also may be used in any sort of your visual communication with customers, stakeholders or developers. It is simple, free to try for 30 days and easy to use. Balsamiq provides various options for web and mobile prototyping.

What I wanted to visualize today is an interesting question:

#2 How does the internet work

Let me rephrase that question: what happens when you type http://www.something.com into your web browser. My Balsamiq-made info graphics – hopefully – would be an answer.

client-server

What the browser is going to do?

Step 1:

It will try to translate your URL into IP address. In order to do that – the browser checks cache (a place where system saves last translation results). If the cache is empty – browser will send a request to DNS server. The DNS server provides the browser with URL translated into IP address. Finally our browser would know the address (a default HTTP port = 80) which is responsible for GET our request.

Step 2:

Server transforms the request and if everything is OK response with the HTML website and at the same time 200 OK status.

Generally, in order to understand how does the internet work, we would have to know the answer to a question – what the HTTP protocol is.

HTTP stands for “Hypertext Transfer Protocol”. The entire World Wide Web uses this protocol. Almost everything you see in your browser is transmitted to your computer over HTTP. For example, when you opened this article page, your browser probably have sent over 40 HTTP requests and received HTTP responses for each.

HTTP headers are the core part of these HTTP requests and responses, and they carry information about the client browser, the requested page, the server and more.

To make my above graphics simpler – we could present it this way – using Balsamiq again:

http

Hope my short post encouraged you to try Balsamiq and use it within your testing tasks.
In case of any comments –  stalk me on Twitter 🙂

Posted in tools

Vysor – tiny tool for mobile testing

talking-tools

This time – not precisely about catching bugs – rather about improving your work as a mobile tester / developer. I know that there are people (still), who never heard of Vysor. This short blog post is for them 🙂

Vysor is a Chrome extension that allows you to share the screen of a mobile phone on your computer desktop. They advertise it as “A window to your Android” and it really works this way.

It becomes extremely useful when it comes to demo for your customer. It is also useful on daily basis. You are able to connect smartphone to the computer and perform clicks or inputs using your mouse an keyboard. Sometimes it’s really time-saving.

Here is a link to some tutorials – but the tool is pretty straightforward.

And remember – to make all work – plug your mobile phone to the computer using a cable and enable developer options. Enjoy!