Posted in accessibility testing, mobile testing

Accessibility testing is your social responsibility #AccessibilityTestingDoIT

1w45l6

New school year in Poland has began, so for me it is time for new professional goals even more than January 1st.

It is almost a year of me writing this blog and if you are a frequent visitor, you may have noticed, that aspects of testing, coaching, agile and conference stuff are mixed up here. It is basically because I do believe that all of these are equally important parts of tester’s professional life. We can never say that agile or mentoring is not our job. It is. Not obligatory for everyone, sure, but still valid.

On the other hand, as I wrote a while ago, I think that working in the fantastic software industry is a opportunity. At first, it is a chance for us to gain knowledge, feel the modern software vibe, know what’s on and simply to make money from exciting activities. Secondly, it is a chance for the others and ‘for the world’ (sounds like Miss Universe, doesn’t it? 🙂 ) to let us make it a better place. I think that testers, developers, graphic designers, UX specialists  can still make a change, not only by creating stunning websites or mobile applications, but also by making the accessible to all users, especially to people with any kind of disabilities.

I’m going to make a series of articles focusing on certain impairments, to give you a chance for having a closer look to the problem and possible improvement solutions. I know that each of you work in different software industry branch, so all together we are quite powerful.

For a tester – it will be a matter of one – two additional test cases or test suite in our daily basis activities – for developers – it will be a better code maybe, for graphic designers an UX specialists – it will be yet another tool to make developers following THE RIGHT path 🙂

pobrane

 

Action points:

Let’s start from scratch:

  1. What is an accessibility testing you can read here in one of my previous post.

          2. Where to look for mobile development tips:

3. Is it software – related subject only?

NO

It is both hardware and software.

4. What kind of impairments would I like to cover?

  • visual
  • physical
  • hearing

I’ll try to create a separated section at the top of this website – so you’ll be able to access content at any time in order to practice your accessibility testing skills.

         5. At the same time – if you have any cool websites, services, books, articles…….. AND SO ON to share with me or with the entire community – don’t hesitate to paste it in the comment, on Facebook.

  6. Tweet any accessibility testing – related stuff using hashtag #AccessibilityTestingDoIT

Cheers!

Advertisements
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!

Posted in accessibility testing, kiss, mobile testing

Minimalism design in testing

alcohol-addiction-awareness-day

Usability Heuristics

A while ago I wrote a few words about Usability Heuristics and what is their role in software testing. You might also heard about the KISS (Keep It Simple, Stupid) rule, which seems also to be impotent is such activities like web or mobile design. In this post I would like to focus on one particular issue (or trend), which becomes more and more popular nowadays. On the other hand, it seems to be just the common sense output of your software development – The Minimalism.

Good application – what does it mean?

Each year Android community chooses applications that were outstanding during the year. Competitions might differ in details, but one feature is clear and repeatable among all winners – good design.

When we are talking about design, we might be thinking “wait a minute, isn’t it an art – related stuff like sculptures, paintings or furniture?” Well – yes. But not only. I’d say that web or mobile app design is as important as it’s final working version. At the same time the role of software tester in development process, who is aware of good design importance, is essential as well. If the application works fine and causes no error, but simultaneously it is ugly – no one would use it. Or – in best case scenario – he’ll use it once (and it’s get deleted 🙂 ). Keep in mind that 80% of mobile applications are being deleted after the firs use. Why oh why? Most of all because they don’t work as expected, but sometimes – because they’re ugly 😀

A stunning example of beautiful, thought through application is Hopper – the one and only last year winner of best apps ranks. I’ll recommend you to download it from Google Play or App Store and just play around. Using this app is so pleasant and surprising like playing with a piece of art.

When I think about examples of good mobile design – I recall Hopper all the time. Pure love.

screenshot_2017-01-18-11-50-15

Aesthetic and minimalism design

Minimalism is achieved by reducing a design to only the most essential elements.

This heuristic states that aesthetic (which is rather a subjective feeling) and minimalism design (which can be measured somehow) are important.

For example: dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility. This heuristic is extremely important to be followed in mobile app design.

Mobile applications are not supposed to be over packed with tabs, buttons or unnecessary content. App designers should keep layout as tidy and simple as possible. That is also a great challenge for the tester in the very last phase of each development – to make sure that all elements that have originally been designed are delivered within the working application. Always remember about the KISS (Keep It Simple Stupid) rule. It’s equally important on each stage of development process.

Testing usability is somehow about taking beauty into consideration.

Following trends

Essentially, minimalism is about breaking things down to the barest elements necessary for a design to function. In addition, taking things away until nothing else can be removed without interfering with the purpose of the design it’s also a minimalists’ routine. Remember, though, that certain design and graphical elements will directly affect the readability or usability of your website. Note, that it might be highly important in accessibility testing.

Minimalism could be applied to various branches of art or architecture, including web design as well. Testing minimalist websites or mobile applications might seem challenging, but possible for anyone.

Before you test anything in the area of usability – make sure that you are familiar with good web (mobile) design examples. It is good to know what’s on at the moment, keeping in mind basic rules as well. Take advantage of big players like: Twitter, WhatsApp, or less known such as: TheMinimalists, NorthKingdom, Sarah Hultin.

Don’t think it’s easier, because it’s simpler

When it comes to minimalism, don’t think it’s easier just because it’s simpler. Because there are fewer elements, you must provide the same level of usability (perhaps even better) with less interface. To balance aesthetics with functionality, minimalist web design is defined by use of space, amazing visuals, vivid photography, striking typography, and an overall focus on the content itself – and nothing more.

save-the-earth

Posted in mobile testing

From QA with Love

from-qa-with-love

Love confession

As today is a Valentine’s Day -I believe that my post should be at least a bit about love. I’ve chosen the anti-valentines confessions in public to the particular mobile app makers (I won’t say just developers), who don’t care about the UX and their users so much that they still deliver their apps to Google Play and feel good about themselves.

The post would be about a particular app and what is wrong with it – not about teams that delivered it. I work within the industry and I know that sometimes people do development that they are forced to do, weeping at night in the pillow. I know. I don’t understand, but I know.

Nevertheless, my choice, as usual,  is completely subjective. This application is in Polish, but it’s so wrong, that I had to place it here. Don’t mind the language – knowing Polish won’t help 😀

The homework not done

The epic. The worst, not only because lack of any logical UX: Lekcja+ (Lesson+).  I swore my private vendetta to this application – just try to download and try to figure out what is it about.

What’s Lekcja+?
An app for teachers, who are supposed to provided their timetables and in-school information. #innovation #PolishSchool #LowBudgetTender #MyEyesBleeding

Tester for the rescue

 

It was Monday afternoon some time ago in September. A friend of mine – who works at school – called me for help.
– Hey, I’ve got this app from school, but it doesn’t work. You know what to do with the apps, could you help me? I’m clearly doing something wrong.

images

I’m referring to version of Android application which has been released in September 2016 – presumably without any testing before (according to well – known rule “We never test our software – but when we do – we do it on production only”).

screenshot_2016-09-11-13-31-56

I’ll start from translating this awesome pop-up which stroke me just after app installation. On the app it’s in Polish:

“Information:

Due to large number of notifications about app lack of stability and some components not working some improvements have been introduced. It is obligatory to clear app data (including user data) to have the app updated.

We are very sorry for inconveniences

App changes include:
– stability improvement
– bugfixes
– minor view improvements”

Like – SERIOUSLY – this is the message they provided users with on production. Hey user – clear app data by yourself, we did some minor fixes, but don’t bother .

The application is a perfect guide What you should avoid when creating an app.

There is no menu, guideline, referral to UX/UI of other known Android app’s pattern and I’m not even talking about app stability or it’s basic functions. I’ve installed it on 3 random devices – and it crashed on two of them after installation.

Clearly – it wasn’t my friend’s fault that it has not been working.

Why developers don’t consider the purpose?

There is plenty of horrible apps out there – BUT – this one won the tender for a teacher’s app. At first – it’s government’s fault that they accepted that level of development and paid for it – but apart from forcing people to use crappy software on daily basics – there should be a work ethics of the developer and a tester.
Someone took money for it.
Someone released it and placed it the Google Play.
Finally, someone thought “yeah, it’s good enough, let’s release it”.

screenshot_2017-01-05-18-00-51

I am idealist maybe. I would like the world to be a better place. BUT why U no think while working. I know dozen of stories when a customer forces the team to make an Android app “just like the iOS one” – destroying platform guidelines and architecture “because it’s pretty” kind of reasons. On the other hand, Lekcja+ is an example of making other people’s life miserable.

This app was supposed to be a tool

It’s not an app which you could simply uninstall after first setup and forget about it. It was “designed” for teachers, who are forced to work with it on daily basis. And think about it for a moment – they (mostly) are non-technical people. Maybe this  app is they first installed app ever. Why – just why-  it’s so horrible!

screenshot_2017-01-05-18-01-20

I just wanted to help a friend. Sadly, I was not able to. Taking into account app’s poor rank at Google Play – I was not the only person struggling with the installation and functions. Poor me. Poor them.

Working for people

Making applications for public sector is hard and demanding work. Agree. On the other hand, it doesn’t release any team member from thinking of other peoples’ needs. In the end, public money means everyone’s money, so we all eventually pay for crappy software. What is more, a friend of yours might be a teacher and at he is struggling with the app at the moment.

We don’t do software for ourselves.

We – I mean all people working in IT industry. We do it for other people. Each user has a name and a job to do. Sometimes they use our software to complete it. You might think that Lekcja+ is not a life-supporting software, so I’m exaggerating. Sure, it’s not, but why forgetting about the user, while he is the one that would be frustrated with a crappy app most of the time.

I wanted Lekcja+ to be just an example of terrible software that we all struggle with.

dear-mr-developeruse-your-empathy-make-the-world-a-better-place-from-qa-with-lovekinga-witko

Posted in kiss, mobile testing

UI goes first. Mobile Testing.

do-somethingkind-today5

You’ve probably heard about usability testing. It’s one of non-functional testing ranges.
A quick reminder about non-functional test types below. Usability is the one that we will be focusing on now.

wwwww

Why testing mobile apps, when Usability comes first is so important?

Because form UX point of view application should be:

  • attractive
  • functional
  • useful
  • fun

Application should make the user happy – not frustrate him. How is it possible to be done? By providing great, clean UI. No matter if we are talking about iOS or Android applications – rules are similar. Keep It Siple Stupid.

What is more, you’ll have to keep two facts in mind:

  • Mobile customers are intolerant and fickle. (You know you are). If your app isn’t a knockout on first impression, it’s probably going to be deleted or will be forgotten on their smartphones.
  • 50% of the users expect, that an app is ready for use under 2 seconds

Silicon Valley analyst Andrew Chen attests that the average app loses 77 percent of its users in the three days after they install it. After a month, 90 percent of users eventually stop using the app. In addition, research by Mobilewalla revealed that users eventually delete 90 percent of all downloaded apps. Make one wrong move that angers or frustrates users – and chances are your app will be deleted.

We could say that testing mobile app is one of the most stressful jobs on the planet – if you don’t succeed – the app doesn’t as well.

do-somethingkind-today10

Even if the UX design is correct during your testing remember about following check list:

  • get familiar with you users (by research, Google Analytics, Twitter etc.)
  • mind screen size (device fragmentation)
  • check on proper OS versions
  • select correct device types and brands (brand fragmentation)

Remember, that in mobile testing, more than anywhere else – tester is in charge – not only by keeping the initial design in shape through all development and testing process, but also by protecting user’s needs.