Day 30 and 31 of the Testing Challenge

Do you know what day it is today? It is THAT day. That day when it would all end… That day when the Testing Challenge created by Ministry of Testing is over. Over, I tell you!

I guess you’re now going to say “Testophiliac, don’t you know how to count? There is one more day left, the bonus day!” That’s what you wanted to say that, didn’t you?! I had a feeling…

Well, the reasons why I combined the two is because:

  1. I couldn’t separate the challenges. Day 30 said to:

    Give someone positive feedback.

    and day 31 (the bonus day) said to:

    Share your 30-day challenge experience on Youtube, Instagram, Twitter or a blog post!

  2. I’m going to the seaside and starting my vacation. In fact, I’m at the seaside now! Sending many waves to you! Not big, big waves, just normal-sized ones.

The bonus day has been fully achieve, as I’m writing this and have written everything on my blog. It’s self-explanatory. And because it is the last day of the Testing Challenge, I would like to give the positive feedback to *drum rolls* every tester out there! Everyone who has participated in this challenge, blogging/tweeting/facebooking (is this a verb?) and others every day for the past month, you freaking rock!

For the ones who haven’t managed to finish or update daily or who just planned to participate, but couldn’t: we get it, life gets in the way of things! But if you continue to learn how to test better and you stick to it, congrats to you, as well! You can find the motivation to get better at your craft and, who knows, maybe there’s going to be another challenge in the future? Don’t give up!

I would like to thank Rosie Sherry from Ministry of Testing for building up this challenge, it was really inspiring and I bet a lot of us have learned a bit more about us as testers and as people! Also, thanks to Tabara de Testare for existing and for keeping its members close and always helping them out. Thanks to Daniel Knott from Adventures in QA for opening up my eyes on mobile testing through his book, “Hands-on Mobile App Testing” (I still haven’t finished it yet, but I promise I will!) and indirectly giving me an idea for a project. Thanks to Neil Studd for his Weekend Testing Europe session and his cheerfulness. And just thank you to everyone who liked/shared/tweeted about the event or what I or others have said! It was extremely helpful and I think it connected everyone to everyone else much more than before.

As for the blog, I will continue to write on it, hopefully something worth reading. Nothing too serious, because humour’s the best, but I hope that something helpful. The next blogpost will be after I have dipped by toes into the sea so many times that I could be considered a fish!

So, thank you to all and congratulations to all! See you in a short time and don’t forget to:

Test on.

A. Testophiliac




Day 29/30 of the Testing Challenge

It’s day 29 of the challenge and besides being the last-to-one day of the challenge, it is going to be my last day at my current workplace, as well. I have taken advantage of the air conditioner and good coffee here enough, I need to search for others, hopefully as good as these. I’m going to miss this place.

But enough about this, we’ve got a challenge to wrap here! So, the task for today is:

Find an out-by-one error.

Wow, and I thought there were already bad news. What IS an out-by-one error?

After checking it out what it means, I saw that an off-by-one error is related to boundary conditions. It’s mostly like when you would want to add a date or your age on a site, which has to be from 18 to 99, and you can add 100. Or 17. That would be an off-by-one error.

So, it’s no surprise when I tell you that I had to search a whole lot to find this one. Will I be able to do it? Even I don’t believe in myself now, really.

*after 4 hours* Well, I’ve got… pretty much nothing. I did find something nice, though. This:

four no three

You can think of this as a duality of the mind a programmer: he wants his code to have a certain output, but from lack of time or being a hurry, things are not what they are cracked up to be.

At least, there’s always us to double check! You’re welcome.

Test on,

A. Testophiliac

Day 28/30 of the Testing Challenge

It’s day 28 of the Testing Challenge and there are only 2-ish days left! My gods, time runs fast.

So, today’s task is to:

Summarise an issue in 140 characters or less.

Here goes nothing:

The issue with this world is that there’s never enough chocolate, and even when it is, it makes you fat just by looking at it.

That seems about right. 126 characters, also, so I’m in the chart. The easiest way to complete this challenge is to write it as a tweet and see the number difference. I guess that was its original intention, but I will just post this blog post of a tweet on Twitter, so that everybody can tweet the tweet from the tweet. Mind blown!

Test on,

A. Testophiliac


Day 27/30 of the Testing Challenge

Day 27 is already here and we’re rapidly getting closer to the end of the Challenge. Oh, noes!

For today’s challenge, we have to:

Say something nice about the thing you’ve just tested.

My take on this is that you can always find a nice thing to say about anything. “At least the app didn’t crash.” “At least it has pretty pictures.” “At least I can shoot laser beams out of my eyeballs.” There’s always a good side to everything.

A few days ago, I tested an Android game called Shadow Jump. The idea behind it is to tap the screen left and right so that the little glittery box would jump higher and higher without bumping into the shadows surrounding it. It’s small and simple, but the graphics are really something as it was built on the Unity engine. The game implies dexterity and speed, and it’s a really good and addictive way to pass the time. For more info, you can check out the app on Google Play here.

I can’t say that I’ve found anything bad with the app. Should I have chosen an *extremely* awful app and say something nice about it? Now, that would have been a challenge! I would have simply answered “At least the app didn’t crash”.

Test on,

A. Testophiliac

shadow jump


Day 26/30 of the Testing Challenge

Day 26 is in the house all day and today’s challenge is to:

Invite a non-tester to a test event.

Serendipity again! Yesterday, as mentioned here, I told you about me having a discussion with my fellow team members about the meetup we would like to setup for the Eurostar conference contest this year. More on this subject here.

Last night, after brainstorming everything we could think of on Hangouts, we finally reached a conclusion. And a date. And a time. And what we’re going to talk about. And it’s going to be awesome.

The idea for this year of the competition is “Learn to test, test to learn” and there’s going to be just that! How else to better learn than from each other? But I shall leave the juicy details for later.

I already asked a friend to come and help us by taking pictures during the event, as we won’t be able to do that all the time. I know she’s very good at it and I hope she’ll like the positive energy from the meetup.

But that will have to be seen! More info about everything soon enough.

Test on,

A. Testophiliac

odd duck

Day 25/30 of the Testing Challenge

Beginning of the week again and this is the last one of the Challenge! Still excited about it? Me, too!

For today, day 25, we have to:

Contribute to a testing discussion.

Hm, that could be a forum discussion. Or maybe a post on Ministry of Testing’s Facebook page. Or it might be a real-life discussion between testers. Yesterday’s post from Weekend Testing Europe can certainly be counted as a discussion (which I haven’t had time to update, I know, but I went to see The Conjuring 2 afterwards. Have you seen it? Really creepy movie, haven’t screamed like that in years. Anyway, I will update that post today. I should stop writing these thoughts in brackets because it has gotten too long. Bye now.), but I could have another discussion.

And the discussion that I will be having is with my team for the Eurostar competition, which I have written more info about it here, in brainstorming ideas and details for the meetup that will be taking place. I can’t say anything yet, but I think it will be smashing!

Test on,

A. Testophiliac


Day 24/30 of the Testing Challenge

Day 24 crept up on us and came in with a really nice challenge, one that some might be talking for some days. Looking at the the Challenge paper, we can see that today testers have to:

Connect with a tester who you haven’t previously connected with.

Well, today is the lucky day for a lot of us out there participating in the Challenge because at 17.30 p.m. (Romania time, at least) Weekend Testing Europe is hosting another monthly session. And we have a special one, too, as WTEU celebrates two years of activity! Unfortunately, I have only participated to one other session which was last month, but I can tell you that it’s an interesting experience and that made me excited to be part of it again!

So, if you want to learn more about today’s session, you can check out this link here. I will update this post with more info after it’s over.

L.E.: I’m writing now post-session today because I didn’t have any last night. Did I tell you about The Conjuring 2? Well, in a way, I did, but in this blogpost from the future *mysterious music*

But back to business. The session last night hosted by Neil Studd and Amy Phillips from Weekend Testing Europe was really, really good. The main theme surrounding it was “Measuring quality” and the question that everybody had to have in mind was “what is quality?”. And, indeed, what is quality? How does one measure it? It’s like this little thing that everyone takes for granted, but doesn’t actually think deeply about.

For answering it, each of us had 30 minutes to look around on the Songkick website and tell at the end if it’s a quality website. Pretty tricky question as everyone had his/her approach about this. Afterwards, we all started talking about his/her opinions on the quality of the site and we dove deeper into subjects such as “Why would quality matter and what are the side effects of poor quality?” and “What do you look for when measuring quality?” The bottom line is that, while most of us had different opinions about the issues at hand, each agreed that the product has to: do what it says it does in a user-friendly way with very pretty pictures. That’s why it is extremely important to know your business, know your product and know your clients. Just by having a messy UI might mean users not using your product from the get-go, but this is a longer story that (maybe?) I might write about in the future.

For more detailed posts about how it went, you can check out this one from the Weekend Testing Europe website or this blogpost written by Neil on his blog. It was a really nice and productive session and I hope that there will be more to come. Congrats to everyone!

Test on,

A. Testophiliac

P.S.: The photo looks like it was made for ants, but I was on my phone and I had NO idea how to (or if I could) maximize it. I didn’t want to press too many buttons, either, because I didn’t want to leave the conference by mistake. You’ll just have to believe me that Neil’s on the left and Amy’s on the right.

Neil and Amy

Day 23/30 of the Testing Challenge

Day 23 is up for some time and I think it’s the perfect day for a challenge, such as this:

Help someone test better.

Well, I guess I have to take back what I said. It’s the third or fourth time when I have to do something with a fellow tester and I just can’t because of reasons I have mentioned here. So, another workaround will have to do.

The first thing that comes to mind is: I’m already doing it! Writing a blog on testing *is* helping someone test better or, at least, making that person understand what testing is and its importance. An example would be this blogpost where I wrote about Day 7 from the Challenge, talking about accessibility issues with examples from an actual website. One of my friends, who does not work in the IT industry, found it really interesting and said that she had also seen websites very tiresome for the eyes even for people without eye problems or glasses.

What I’m trying to say is that every bit of testing explained or shown to other people, even non-technical ones, might make a pretty big impact on them and help them realize just how important quality is. They might start looking for problems in apps and websites themselves, who knows?

Now, go forth and spread the knowledge! QA needs you!

Test on,

A. Testophiliac

helping others

Day 22/30 of the Testing Challenge

Day 22 has come and it’s a Friday. Aaand that’s it.

For today’s challenge, we have an interesting:

Share your favourite testing tool.

I haven’t had the opportunity of trying out a lot of testing tools, but from the ones that I did, I can say that I mostly enjoyed Postman. Maybe it’s because I really liked testing REST APIs, which was something completely new and unheard of to me about a year ago.

REST API is short for REpresentational State Transfer and you can see more about it in this Youtube video. I find the explanation simple and straightfoward, just as we all should like our info. So, it’s about a call made from the client to a server using the HTTP protocol. The client asks for something or does an action and the server replies. How does the client do those things?

Let me give  you this simple example: we’ve all clicked a link and been redirected to a page where there is a “404 page not found”, right? Well, you’ve just requested the server to display a page, but the webpage was not found. It might have been moved somewhere else without having the URL changed as well, actually removed from the face of the Internet or you typed the URL wrong. This is the big picture, but let me break it for you:

  • You, as a client, need to ask the server something and you do that by using an HTTP method. There are more of these, but the mains are: when you want to be returned some info (the GET method), to add some info (the POST method), to rewrite some info already in the system (the PUT method) or to delete the info altogether (the DELETE method). You can find more about the other ones here.
  • The message you’re sending has to be directed to a certain place. Else, it would be like running around on the street asking a question and hoping someone would answer. Those are called “endpoints” and they are just unique URLs to which you make your call. You also need HTTP headers, which operate the way data is being dealt with.
  • The reply. This is what the server tells you to what you have asked. For example, in the “404” situation, the “404” you see is called an HTTP status code, but some even have a body with some more info. There are more types of replies, which can be found here.

Warning: an explanation of a fictional situation created by me to better understand the idea of REST API will follow. For those not interested, skip this big block of text.

You have a couple of objects in your system, let’s say, bunnies!, that have different colours and you want to see which bunnies you have left because there was this mean tester before you that hated bunnies! So, you write the endpoint of where you would find the bunnies, the headers and you use the GET method. After sending the message, you will (ideally) receive from the server a 200 HTTP status code, which means that the server has successfully received your message, and a body (in JSON or XML, whatever you choose) that gives you back all the bunnies. Now, because there are never enough bunnies, you can add a new one with a unique name. You add the necessary endpoint for that (different than the first), the headers and use the POST method, where you can add the bunny that you want with an appropriate JSON or XML code. If things go well, the reply to this would be 201 HTTP status code, which means that your bunny has been created. If you were to make a GET call, you’d see your new bunny added! But what if you wrote the bunny wrong? Then, use the PUT method, where you usually have to write the name or ID of the bunny that you want to change and the new name. So, what if you want to delete your bunny because it is old and tired? The DELETE method would do the trick, using the appropriate endpoint, the headers and the ID of the bunny that you wish to delete.

Warning off: Now it is safe(r?) to read.

Well, I found Postman to be a really cool tool for that, especially that you can organize all your calls in collections, so that they’re easy to use and find, and that they can be backed-up in the cloud, so you can log in anywhere and you will have your calls there. Also, Postman can be found on the Chrome webstore, so you don’t download it, you just add it to your browser. Cool, isn’t it?

Test on,

A. Testophiliac


Day 21/30 of the Testing Challenge

It’s day 21 and my foot from yesterday is fine and dandy, if you were wondering. Thank you!

For today’s challenge, we’ve got:

Pair test with someone.

As mentioned before here, I don’t have a team per se, so pair testing at work is out of the question. I then decided to give a shoutout on Twitter, but no one answered my crying calls and I kept wondering why I haven’t started this challenge way earlier. Finally, I asked these guys for help, as I was desperate:

In fact, I asked only one of them, but the other one insisted, so he came along, too, I suppose… We’ll name them Mr. Sheep and Mr. Bear (from left to right) for maximum imagination and they’ll be testing an app on the iPhone while I try out the Android smartphone version.

After 20 minutes, I had already found a few problems with the app and I asked them if they saw anything suspicious. Neither of them said anything, so I presumed they were in deep concentration. After another 20 minutes, they still wouldn’t reply and I knew these guys were pros, testing without even turning on the phone and whatnot.

At some point, one of them fell on the phone, maybe from great exhaustion?

Looking closer, I saw that the iPhone’s battery had died a long time ago.

I understood and left, feeling wiser than before.

Test on,

A. Testophiliac