Posted in test automation

It is (sometimes) a good idea to automate your regression testing


Desejando-lhe uma

Let’s start from Wikipedia’s definition of Regression Testing:

Regression testing is a type of software testing which verifies that software, which was previously developed and tested, still performs correctly after it was changed or interfaced with other software. Changes may include software enhancements, patches, configuration changes, etc.

Now, when we are aware of what is all about, let’s get to the point.

How often do you proceed regression testing? Once per sprint? Once per month? Daily?

Here we are. If our regression testing is supposed to make any sense – it has to be performed as often as possible – at least on sprint basis. Ideally – daily. Why? Because  stable test suites would catch any unexpected system behaviors and react to a major change.


There is yet another question – how big your system is.

Small systems usually have rather checklists than test suites. Large ones – even the monsters:)
Deciding what should by automated  is always tough, because having automated test scrips may be just something you could show off with or present in front of the customer. I would rather ask: WHY do you want to automate anything?

The problem is that sometimes automated suites don’t test anything (or anything meaningful) and the effort to keep them alive is big.

If you wonder if it’s worth to automate repetitive stuff? I’d answer – sure mate!

Automation is good. But it is just another tool – NOT THE PURPOSE.


I think that automated regression tests might be brilliant and helpful, but you have to remember that you’ll have to take care of them and update them often. You’ll also spend way more time to prepare test suites than to proceed simple tests manually, so if the testing is not repetitive – it’s good to calculate what is more beneficial for your project.

When automating things – you improve your skills and gain time for other activities – so it’s basically a matter of time – the time you’ll save on running automated regression testing and time you’ll waste (it’s not wasted, I know) on preparing them.

I’m just the beginner , so I might be wrong. Don’t agree? Comment below or stalk me on Twitter.

Posted in agile

Tester is not the quality police

Testeris notaquality Police (2)

I wish I could invent this sentence, but unfortunately I have not. It’s been a while when people discuss the subject on Twitter, so I would like to give my short comment on that as well.

The whole team approach

During my panel about being Jedi tester, people agreed that agile tester:

– executes tests
– gathers requirements
– chases designs
– keeps good product quality
– has technical knowledge
– does multiple tasks apart from testing

He is Agile. Whole team approach. Right. Have you ever heard about developer doing things mentioned above? Or about a developer who gathers requirements, chasing for designs, organizing project or taking care of the quality a whole?

Neither do I 😀

So where is the whole team approach?

For some reasons, it happens sometimes, that a Project Manager, who is introducing the tester into agile (not only) project, thinks that having a member of QA in the team solves all of the  problems. Tester would be some kind of policeman watching developers and defending the code from bugs.


I do agree that tester’s role and certain approach to developing good quality of software products is unique and is a must, but when other team members don’t care about quality – tester’s effort is pointless. The whole team approach means that everyone is responsible  for the product and have good quality in mind.

When we succeed – all of us can celebrate. When we loose – the whole team looses – not just a developer or a tester.

Software tester cannot be a policemen who watches the code. Some people may say that he should be a quality evangelist, who teaches developers proper approach of dealing with code and bugs, but without certain mindset and maturity of team members – single tester is not able to cope with difficulties. He’s role is important, but he is not able to change anything alone.

When thinking about agile project – all of us should think about quality – starting for Project Manager. What is more, each developer should be as quality aware as possible.

On the other hand, tester is a person, who points the purpose and leave some breadcrumbs for developers in order to help them, but the act of quality is whole team’s responsibility.

Don’t think about the testers as villains or policemen. We are neither of them. We care about quality and do our jobs as good as possible 🙂



Posted in Uncategorized

You follow the leader, because you want to

when we honorthe earth, we honor ourselves

You follow the leader, because you want to…

you follow a manager, because you have to.

This very simple truth that I’ve heard some time ago might fit to your professional career as perfect as it fits to mine. Some smart guy said to me a few days ago that people join the companies, but leave managers. This is so true.

I always thought that joining the company and considering their values and principles as important are consistent with mindset of all people inside them. Apparently – it is not. Even when company’s values are perfect and eye-catching through recruitment process for you – the real values and day-to-day behaviors of their employees may differ as much as many people work within it.

However, it may not necessarily mean that employees harm company values on purpose. Sometimes people join certain companies, because some benefits such as: technology, brand or possible profits are equally or more valuable for them than the company values. Nobody gave me the right to condemn such behavior.
On the other hand, it might mean that your manager doesn’t share the company values, which are important to you. It might also mean that your manager would not be the best leader in the world. It happens.

when we honorthe earth, we honor ourselves (1)

The Earth is not as flat as you initially thought it would be

Let’s assume that company A strongly believes that Earth is flat.

Accidentally – you – the great geologist – believe that as well. What a coincidence!

The Earth is flat – finally somebody said it out loud! You start your recruitment process believing that you’ll change the world and FINALLY the truth will be revealed to the rest of the humanity.

All goes well and you’re joining Company A. You start your geologically – centered work and at day 1 meet Jason.

Jason is your manager.

Jason joined company A, because it is a known fact that they pay well and this is what he was looking for. On the other hand, Jason is personally strongly convinced that the Earth is not flat, but it is a tiny cube. He didn’t revealed it through recruitment process and no one noticed so far.

Jason was promoted to be a manager in company A, because he was dedicated to his work, his professional experience was flawless and his passion to tell people what to do was great. His personal believes are now started to be more visible, but not as important for the company as his performance.
Pro: Jason is a great asset for the company.
Con: He starts convincing you that maybe the Earth is not as flat as you initially thought? Maybe it is more cube-like rather than being flat?

In Polish we would call it “Sytuacja ambiwalentna” – you’ve joined the company in the first place, because you’ve shared the same values and – at the same time – you’ve been given the manager who doesn’t share those values at all.

Sometimes it is not possible to change your manager or project. Surprisingly, it may be way easier to change the company.

I won’t say that this situation is common, but it happens. As I wrote at the beginning – you follow the leader, because you want to – you follow the manager, because you have to.

It was always funny to me all those LinkedIn’s pictures showing how the REAL manager should behave in order to encourage people to be more effective at their work.
Today, I think that meeting a real leader is important to everyone’s professional career – no matter if the leader is running the whole company and is simply an inspiring person – or –  is your closest manager. Being led by wise, hard working managers, who share the same values as you do means more than money or benefits. Everyone would prefer to follow people, who support them, show them how to achieve their targets.

We spend most of our working days at work. It is a lot of time. We could use it wisely or not. It’s up to us.

I wish all of you to meet leaders only. Be inspired by them and make the change.
Don’t let yourself be managed by poor managers.
Don’t stick with the companies who promote poor managers.

The Celebration Continues!


Posted in conferences

How to become Jedi tester


Lady Vader

That will be the blog post explaining where my new nick name is coming from:) And, in some more details, what my discussion panel at the Test:Fest conference was about.

Can you see the picture above? I used that to describe myself instead of my personal one. Best idea ever. Thanks to Tomek Olszewski – one of the Test:Fest organizers – I become “Lady Vader”.



As you probably know, I had an opportunity to speak at Test:Fest conference that took place in Wrocław last weekend. Title of the discussion panel was “How to become Jedi tester” and I tried to combine agile ideas with Star Wars background there. You’ve asked me if I could write something more abut the panel itself. Let me try:)

My biggest fear was if anyone would talk during the panel, but apparently everyone was eager to speak:)

As agile is my favorite working approach and methodology – I like to talk about it and hear people’s opinion. I believe that everyone would like to be the real Jedi – why not to become Jedi tester?

Our force is quality:) We have power!

My Jedi-related panel consisted of 3 main areas:

Do you Agile?

Will “Tester” survive?

Is agile certification worthless?


It was clear very soon that everyone understands agile in a different way. Some of attendees thought about agile as a whole package (team, scrum, kanban, retrospectives), others implemented just some elements in their projects. On the other hand agile is the ability to be adoptive to changing project environment, so that was also an issue during our discussion.

There was even one brave-heart who confessed that he works in waterfall (We support you). Discussion was vivid, so I am happy with the result.


Will “Tester” survive?

My point is that when we’re talking about whole team approach, roles of each team members should consist of : PM, BI, dev and test duties. During the discussion it occurred to us that everybody thinks that this is a tester role to adopt – to be agile. Did you hear about developer gathering requirements or testing (by heart) his own code? Nice output btw.


Is agile certification worthless?

I’ll leave you with this question as there is as many opinions as people. Should you have any comments, write them down here or tweet me.

I would also thank everyone taking part in the panel and discussion, it was a pleasure to meet you.


Posted in conferences

Test:Fest Wrocław


My first time as a speaker during testing conference

It won’t be a objective opinion about Test:Fest conference that took place in Wrocław (Poland) yesterday. It will be highly subjective, as they allowed me to run a discussion panel about agile there 🙂 #fame #MeSpeaking

Apart from this amazing fact, I would like to give a short feedback from attendee/speaker’s point of view.


This free conference has 3-year long tradition now. People, who put it into life, dedicated their spare time, over hours and plenty of good will to make it happen. This year the event was amazing – over 400 attendees, 26 speakers and whole-day event. Awesome.




All presentations were great and well prepared – my favorites: Antoni Roszak (Wojna o jakość, czyli co ma lotnictwo wojskowe do testowania) talking about battle that testers fight for quality and Tomek Dubikowski (Level up your Quality) with his game 😀


My debut

The most stressful for me – talking to people about agile and getting feedback. There were surprisingly lot of attendees at my discussion panel (How to become Jedi tester). Discussion was vivid and involving. All went quite well, so I think I’ve done my homework.

I had the one and only supporter Daria – who stood behind my back and was amazingly supportive the whole day and during the panel.


In the end – my presentation was ranked as 3rd best so… not bad, isn’t it? I believe that everyone now is able to be the real Jedi tester in their teams.



I am very excited that I had an opportunity to meet people and talk to them. I love such events as this is a unique chance to meet people that I basically know from Twitter or Facebook.
The whole event was great success. Starting from crowded reception with dozens of people waiting for registration, through well-organized coffee brakes and amazing spot, to the calm and chilling after party. You can feel that Test:fest is created by people and their involvement.
Testing is growing in Poland, so do we!