Posted in mobile testing, production bug

The power of “what if” testing



I may be repeating myself, but today we’ll try to think a little bit about a matter of testing outside the box and companies’ reputation on the market.

Most of you, my Dear Readers, work on big software projects. Not all of you in agile ones. As I found out recently, there are still tons of projects that in the field of testing follow very structured and organized test plans, cases etc. It is all great because without your work major bugs would never be discovered.

Today I would like to highlight edge-case testing – all those “what if…” situations that may be not spotted in regular test scenarios. You can always take a step back to see the purpose of your job. I mean it. When you rush in the project work, it is always to little time to look around you. It’s possible, that sometimes you are too focused (or focused enough) to obtain your in-company, in-project testing goals, so you are missing some important factors that make software GOOD.

My purpose today is to convince you that sometimes is good to take a step back and have look on the product, to test outside your comfort zone or, possibly, to ask somebody else to pair with you in testing. Such activities might improve the overall product quality, and make live users – like me – happy and calm.


When I was at the beginning of my career as a software tester, I thought (and I believe
I was also told so), that if I try hard enough, my product will be bugproof and bug-free. The more projects I took part in – the more I realized that it is not necessarily true.
At least some of ISTQB statements are right – software will never be bug-free, and you are not able to stop testing. There always will be something to test, something to improve. On the other hand, some of us – testers – often fall in the trap of checking.
No matter if we write automated test scripts or just repeat series of activities on well know the product. Unintentionally we suffer from pesticide paradox in our projects.
I was in such situations several times by know, when, after a period of really hard project work, I thought that I did everything I could to improve the quality. How big my surprise was when the bugs come back from live customers.


Not thinking outside the box is one of the hardest testers’ sin. Let me give you a recent example. Some of you may have heard that Apple experiences issues with their product updates. There were situations reported online about devices going on fire after an update (wow).

It sounds spectacular and not as breathtaking as this reply from Apple Support (wow):

“That’s definitely not expected behavior. DM us, so we can look into this with you”


I believe that the end user could have been upset and even frightened.
Does it mean that Apple doesn’t test the updating process of their own software? I don’t believe that. But, on the other hand, even such big companies seem to omit some edge cases in their testing process, in the great rush of introducing innovation.
There is more this week from Apple Support. One of my favorite Polish travel vloggers – BezPlanu – put a message on Facebook:

This Sunday I was supposed to present the last chapter form Venezuela. Unfortunately, using fast Chile’s internet, I’ve decided to install the newest iOS update – Mojave – on my MacBook. My computer requested it for two weeks. I’ve ended in the position where I’ve lost everything – including half-done new film (plus part of my Lima recordings and part of Santiago recordings) – they have not been archived on an external disc. After 4 days of the fight and dozens of phone calls with Apple consultants and other specialists, I’ve acknowledged that “it happens when updating” and “you have to back up everything” and it is normal that a computer worth 22 000 PLN could not handle the OS update…

A piece of advice from Apple care was to back up your data before software update. Sure.

And again, it doesn’t mean that they have never tested that, maybe they have, but overall it influences the whole product reputation. The product reputation is not only the matter of marketing but something that identifies the work of all employees, developer, testers, and people involved in creating this software.

It reminded me also of the same situation I had with my Samsung a few Android updates ago. My SIM Card died after the update. The ‘funny’ fact was that no one reported such situation online before. I just got used to such situations in my tester’s life. Lessons learned – always do the backup in case somebody omitted update tests on your device / SIM card model.


Why am I pointing that? Because I believe that, as the software testers, quality evangelists, we are responsible for thinking outside the box and trying to fit in user’s skin. What the user would do with our software? What might be the craziest thing that comes to my mind? What if I…? and so on. It may allow us to avoid some expensive mistakes. I think that we should always consider event the least likely “what ifs” – especially when we work for the well-known company because the equation is simple – the better known the company is – the more expensive are our mistakes. They cost money and – most harmfully – reputation.

Tiny last example from last week.
I’ve started attending German classes in order to improve my language skills. One of the tests on the course was to change the language on my mobile into German. The fun has begun. Not only some of my applications started to throw errors – they event were lost in the UI layer.


It seems that Instagram is not dealing properly with German names that might be long and uncomfortable for UI, especially mobile UI. Fun! But embarrassing. But Fun 🙂

As a summing up – I would like to encourage you today – in your own projects – go tomorrow to work and test something unexpected: backup, installation, simulate network change. Do something potentially crazy, something outside your range of responsibilities. Pair with your non-technical friend or let somebody else test your software (if possible). It is possible that such action, from time to time, may save your company’s reputation and some money.

Good luck bug hunters!

In case of any comments – stalk me on Twitter.



Hi Boys and Girls,

I know you are all here in order to read about my UK adventure at UK Star conference.
It is going to be a loooong post, so grab your coffee/ tea, gluten-free food and keep on reading:)

Some time ago, a friend of mine said that if he would speak at the UK Star conference, he would have given up speaking.
Do I feel the same? Was it that exciting? I definitely pushed my limits. I feel satisfaction and I recommend you all to attend next call for papers 🙂


Let’s go back to square one.
I arrived late at night, as Ryanair decided to postpone my flight for over 2 hours. It may seem weird to you, but before that day, I had an opportunity to be in London just once – approximately 15 years ago (yup, I’m THAT old), so I didn’t know what to expect.
Not surprisingly, modern London is huge, and even more diverse as expected. What is more,  the city looks like an enormous Lego – construction work set 😀 There are cranes and scaffolding everywhere. I felt intimidated and overwhelmed since I arrived. It was raining, of course 🙂




Conference’s location, in The City, was extraordinary. It corresponded strongly with London’s vibe and diversity. Inside and outside the building it felt the same – multiple languages, opposite minds and full of fresh concepts. Beautiful interiors and professional service made it all work. We’ve been kindly hosted and no one from conference attendees felt excluded. Just from the first moment something ‘was going on’ and everybody was engaged.

Before the conference begun I felt nervous and was extremely unsure. Me – a foreign girl – not speaking English English – in the middle of a big city.

After a funny moment during the registration, when a volunteer was not able to find my badge (because my name is pronounced completely different than it is written in English), I’ve decided to start from tasty coffee. Coffee is always good to start with 🙂

Just after a few seconds a girl approached asking me about my talk and exchanging ideas in the field of accessibility testing. It was probably the first time when somebody knew me from YouTube or my blog and wanted to know me in person. I was honored. It gave me a lot of self-esteem 🙂 Go Scotland! 🙂



Before my talk, I had a chance to meet a lot of Twitter friends and finally get acquainted with them in person. What a wonderful moment, when you are able to talk to people that you admire for what they do as testers and speakers, who inspire you for a long time and you can just talk to them. This is why you should attend such events. The presentations are important, for sure, but for me, the vibe, spirit, all fantastic opportunities to talk to people were definitely more valuable that day.



I can name a big difference between Polish conferences and UK Star. In most events in Poland, attendees are the people who start their journey with testing, who want to learn anything, something to start with. They look for basic topics and workshops in the area of test automation or manual testing. At the UK Star, I had an opportunity to meet testers from different countries, with at least several years of experience within multiple projects, who came there to share their good practices, achievements and just to inspire.

As you are probably interested not only in my feelings about the conferences but in the presentations as well – I’ll try to give you some main topics and walk you through the talks I will remember.

Let’s start from the best keynote I have ever a chance to participate in – Isabel Evans – ‘Leadership, Fellowship, and Followership‘. It was my first opportunity to meet Isabel in person. Her very personal and inspiring talk led the audience among different styles of leadership and peoples’ behavior.

I’ve acknowledged also that being compassionate to yourself is a key to everything – being a good human, employee and a leader. The rest comes second. We should leave the world a better place than we found it. I find this keynote strong and a must to be heard live. If you ever had an opportunity to hear this particular keynote live – do not hesitate and attend!

I’ve also learned that our leadership style is strongly determined by the company and its rules. If there is a capacity for playing and making mistakes – there is also a space for the team’s evolution and growth.



Christina Ohanian, the Tester, and Agile Coach performed her opening keynote session – ‘Embracing Change‘ at the very beginning of the conference. I bet my manager – Piotr -probably the biggest fan of Simon Sinek in the world


would hear this talk with pleasure as I did. There were several referrals to Simon Sinek during the whole talk. To build a good test team in your company – you should definitely start with WHY and define your purpose all the time. All may change, but there should be a purpose always.

As Christina said, change is scary, especially when we are used to a particular way of working. Learning to embrace a change and adapt to the environment around us is both healthy and urgent necessity.



I need to mention @thetestdoctos ‘s – Dan Billing – the workshop about security testing. Finally, I had a chance to meet and hear Dan in person. We had a lot of fun during his presentation, as it was a PROPER WORKSHOP – WiFi was not working, there were no tables for the laptops and time was limited 😀 Dan is sneaky – he wanted us just to feel a little bit of security testing in order to invite him for a decent workshop in our companies.  Best PR ever, Dan! 😀

We’ve learned that hacking is illegal. I am disappointed with this fact 😦 I’ve also noticed, that opposing to movie stereotypes – you don’t need to wear a black hoodie (as I had none that day)  and you don’t have to have a wall of GREEN PHP code in front of you displayed in order to perform security testing (aka hacking). Oh maaaan. Such disappointment.

But seriously, you should definitely invite Dan to your company!



UK Star was not only about presentations and workshops – there was plenty of space to talk and exchange experiences – either within Lean Coffee meeting in the morning, in the Test Huddle area or during conversation tracks such as ‘Ultimate testing Survival / Zero to One: StartUp quality notes‘ prepared by Victor Slavchev and Yann Person. They were able to involve the audience into the conversation and bring the value to the whole discussion. From Yann’s part – I loved the most a statement saying that startups begin investing in testing just after first production failure. On the other hand, Victor’s crazy slides convinced us that we should emphasize our value as testers within our companies, as quality is an integral part of software development – not just a part after development phase.



Finally, there was also my talk – ‘Make IT accessible‘ happening that day. I was placed in the agenda within a storytelling track – together with Rick Tracy and Lena Wiberg.


I had a unique opportunity to speak up about accessibility testing and why it is so important for everybody. People were listening to me, nodding, participating in my short exercise. It was even more than I expected. I had a chance to talk to some individuals from my audience about accessibility, that gave me the feeling that there is a need to talk about it over and over again. As I believe, that no one should be excluded from our society by the software, especially people with certain physical or mental disabilities. This is our responsibility as software developers, testers, UX designers to care and to make our applications accessible.

At the end of the day, after all my preparations, it just felt great to stand there and talk.




UK Star conference was important for me. It brought value. It matters.

The conference has it’s flawed as well, of course, it has, but this time I decline to focus on them. It just was great to be there.

In case of any suggestions – stalk me on Twitter or put your comment down below. Cheers!

UK Star. Checked.