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 Uncategorized

#Changes

IMG_1651

I’m baaaack 🙂

Three fantastic news to be revealed at the same time, as I promised.

Thrilling news No.1 as a main course:  
My journey at UBS is over. It was a fantastic time and I’ve learned a lot, however, now it is time to move on. As some of you already know, since September I am beginning my adventure with New Voice Media.
I can’t wait and really looking forward to do some awesome things in the area of testing and agile.

Social news – as No.2 –
I’ve started a Facebook page https://www.facebook.com/KingaTest.blog/ to keep in touch with my (not only) Polish readers. It will be in Polish:)
I’ll try to post there updates about fantastic testing events (not only) in Wrocław and maybe more of my mobile-related discoveries. Fell free to Like!, Share or contact me through this channel, comment articles, posts and whatever you wish.
I wish it to be a common social IT-related space.

Conference News No3. –
September is going to be a busy month – I would like to meet you all at 3 fantastic events:
21st – QA talk at DataArt Wrocław
23rd – Wrocław Agile Day
28th – SeeTest in Sofia

Let’s meet and have a chat!

And exciting news No.4 –
I do believe that working in IT and earning money obliges us to help the others, who were not as lucky as we are – especially people in need. I always try to support various initiatives such as SiePomaga, Fundacja Gajusz or Fundacja Anny Dymnej.

Can we do more?

Together with quite large group of people from UBS, Credit Suisse, Epam, XL Catlin we’re preparing A MUSICAL called Freedom.
Yeeeeeeeeeees. Kinga Witko will be singing (and dancing – oh Lord) 🙂
All for Fundacja Jaśka Meli.

We do it for charity, but have amazing fun at the same time 🙂

Imagine bunch of IT and bank-related people singing and dancing on a real stage. 🙂 Insane. That will be huge! Our project lasts for couple of months now, but currently it speeds up! Great premiere will take place in April 2018 in one of REAL theaters in Wrocław. I’ll try to keep you updated on social media, as it’s now official 🙂

I would like to invite you all to Wrocław in April to be a part of this fantastic event, but in the meantime – you can support Jasiek Mela – or any other people in need.
Let’s be the change!
Let’s be open.
Let other people grow.

Cheers!

Posted in agile, scrum

I had scrum once. It was… fantastic!

National Sunglasses Day Sale

Hey People!

Why sunglasses at the beginning? It is 34 C degrees in Poland at the moment. Really hot – so sunny kisses for those of you –  who have milder weather conditions:)

Reason No 2 – it will be my last post before well deserved holidays (you can be jealous). Some major changes are coming just after the holidays, but let’s keep it in secret for now;)

Why Scrum again?

After my previous post I was asked if I had an example of nicely done retrospective meetings. Can I recommend some approaches?

I decided to leave theory and books aside for today and focus on practice. This is a unique opportunity of real-life project retrospective memoirs.

KingaWitko_QualityExcites

Step one – Communication

There is no Scrum, no Agile, no retrospective when people don’t talk. How to obtain it when not working at one spot? The other day I’ve heard of great approach “Pretend you are all remote”, even if some of you is sitting next to each other.

What’s the benefit? We are all at the same page. We are able to talk with the whole team  and at the same time, no one is excluded from important sessions or decisions. From tester’s point of view it is highly valuable.

My experiences with remote work and remote retrospective meetings used to be bad, very bad, actually. When people were sitting in two or more locations – the knowledge, skills and social life were divided as well. Retrospectives were rather rare and ALSO divided. People gathered in some conference rooms, were not able to hear well, some of them were excluded. Do you have such experiences as well?

BUT

The change has come.

Unique approach

I had a chance to work in a scrum project once. The real scrum project – with a scrum master, great mindsets and whole bunch of good  Agile treats 🙂
It was not a long-term, but definitely outstanding one.

We were located in three cities, but it was not important. Development team was at the same page all the time. However, great communication and demanding tasks were not the only features that make me think of this project as of the good one – retrospective made it remarkable.

What was so unique? Does remote retrospective really work? Sure it does! All you need is approach, sense of humor and the purpose.

The meeting

b1e3c46ef8f1cf9f45d808c9a0bf934e--secret-meeting-picture-cat

Nah, not that kind of meeting 🙂

I’m rather talking about such level of curiosity :

FUNNY-CATS-we-can-haz-council-meeting-meme
First of all, meetings were recurrent – same day, same time each sprint.
As I wrote before, the need of ritual is essential when talking about retrospective. Next – it was fun!

The scrum master took us by surprise each time. He provided awesome and delicious boards (online boards, of course), on which EACH OF US were welcome to “stick” their notes.

It was virtual – but it worked perfectly well. Going this direction, we had:
doughnuts retrospective, candy retrospective, pink fairy retrospective and so on…

Some of us complained that it is not “serious”, “somebody bought Creative Retrospectives book” or so. We played each time a bit like kids, but at the end of the day everyone benefit from it.

I also would like to highlight, that the funny form and elements of joy were not that important as the method, that made everyone speak and look for both:

  • fields for improvements
  • good things to honor.

Examples

650fa4f6d721280122a5f518122cef3a
How were we able to obtain that? By ‘talking’ or ‘thinking’ for somebody else. What do I mean by that?

Let’s try to rephrase a standard question:

What you are particularly proud of after this sprint?

or

What was not correct in this sprint?

INTO

What a person, who sits on your right thinks about it?
What he is proud of?
What did he achieved?
What was his blocker?

This little magic trick enables your mind to completely different behavior. It helps you to become a team, to acknowledge someone else’s needs and before the next meeting – you’ll ask first:)

As i said, each time we had surprise. Games were different, surrounding was different, but eventually it made a team – and this is all about in Agile, isn’t it?

Catch me on Twitter, I’ll keep you posted (and make you angry) from sunny beach 🙂 Cheers!

 

Posted in agile, scrum

Retrospective – it matters the most

Is it me only, who thinks that this blog becomes more and more Agile than testing? 🙂

Anyway.

retro

The other day I was trying to describe myself in front of big audience – and I thought that the best sentence would be : a software tester, who fell in love with … agile methodology! 🙂 A friend of mine asked me if I am more a tester or more an Agile creature. As everyone is Agile now – I’d rather  stay with tester’s mindset but Agile way of work. Does it make sense?

Speaking of which – what is the most important meeting for you (if you work in Scrum, of course)?

For me, when thinking about Agile, the most important and valuable meeting that comes to my mind is RETROSPECTIVE. You may agree or not, stating who we are without daily? BUT in my opinion, a retrospective meeting is unique portion of time, when the whole team sits together and tries to improve.

Team as a choir

hqdefault

Let’s imagine that a Scrum team is a choir.

It has to practice, sing and perform together, exchange ideas, spend a lot of time with one another. They do work.
On the other hand, each of choir members practices alone. Each of them knows his notes by heart and can perfectly sing solo parts, but at the end of the day – they have to perform in front of the audience. The performance of a choir is not a bunch of gathered solo parts – it has to sound as one! All voices complement each other and act like human orchestra. Can you imagine your team acting as one organism?

When thinking about this kind of approach – it may become obvious that scrum team has to seat together and have a common goal. For me, a retrospective meeting is that period of time, when a choir meets, has a rehearsal, spends time to improve and acts together.
I do believe that as  voice rehearsals are the most important times of choir work – as daily meetings and retrospectives have the same roles in scrum team lives.
It is all about acting together in order to improve.

The need for ritual

shareimage

In one of my favorite books about retrospective meetings – Agile Retrospectives: Making Good Teams Great (you can find it on Safari or Amazon) – retro meeting stretches across the whole sprint.
It is not just a meeting, of which everyone would not remember the next day. It lasts. The need for ritual is essential in preparation, conducting and improving. It is always about those three factors. That’s why everyone is welcome to come with his own opinion, problems and successes to the meeting. It is not supposed to be a one-man-show but a choir performance (or just a rehearsal 😉 Everyone is involved!

Leave your negative energy behind

How to act as a choir during retro? How many retrospective meetings, on which one person was a dominant do you have behind you?
Most of us have plenty of negative experiences connected with retrospective meetings (especially in Poland, when everyone is more tend to complain that to cheer up 😉 – please watch this YouTube video by Mark Walters to acknowledge what does the Polish Face mean 🙂 ). BUT complaining should not hijack the retro spirit !!!

Negative packaging is the first things the listeners see. Complain energy is tricky to handle. That’s why each of you should come to the meeting with your own mind. That’s why scrum masters use “stupid” games, “ridiculous” colorful sticky-notes and act (sometimes) like children :). Simply, in order to avoid a situation when only one person, one point of view and one problem matters. Everyone should be influential and benefit from the meeting.

A developer

banana-minion-wallpaper-despicable-me-movie

A development team consists of… DEVELOPERS! Brilliant, isn’t it? And as we all know – developers are the most open, cheerful and ready-to-speak up people in the whole universe!
83ae4322dff2116546d025b11f793523

So… sorry, Scrum Maters, Product Owners and all business-related people – it is not an easy task for you to make them speak during  retrospective meeting:)
How can you encourage a technical person to do so?

Honor the heroes!

Bring sweets!

Hear success stories!

Don’t push!

Capture and analyze metrics  (technical people feel more comfortable with numbers)

Bring more sweets!

Always look on the bright side of life

leadership-lessons-from-minions-550x336

Exactly. Speaking, complaining and honoring mean nothing if you don’t benefit from it. Sooooooooooooo – get it done!

Collect ideas in order to improve. As a choir during rehearsals:

practice, improve, repeat

Summarize your thoughts in an email, wiki or any other source of common project knowledge. Make your ideas and improvements visible.

Buy yourself a whiteboard, prepare a virtual Jira board. Do at least one thing to emphasize your conclusions, enable each team member to have an access to it.
The more you know – the more you are able to improve.
And remember – your conclusions from Reareo No1 might be a great beginning of Retro No2 and so on. It is a circle and a teamwork.

Good luck! May the retro-force be with you.

In case of any ideas – don’t hesitate to stalk me on Twitter or comment down below. Cheers!