5 reasons why you should attend RTC this year

Every spring Romanian Testing Conference is the event that gathers hundreds of quality lovers, software testing enthusiasts, manual testers, automation experts, men, females, teenagers, companies, sponsors, people who want to learn more, hear more, interact more, all sharing a common passion – software testing.

Every spring we see new faces, we hear new stories, but we also see familiar faces that have been with us during the years.

And every spring we are so happy and grateful to have all these people joining us in creating the biggest software testing conference in Eastern Europe.

If you’re asking yourself what makes Romanian Testing Conference so special, you are in the right place.

Here are the top five reasons why quality lovers should attend Romanian Testing Conference 2019.

#1 International Networking

You can get direct access to our great speakers and get insights about their job, their experiences, their testing stories and why not, get inspired by their way of doing things.

We truly believe and encourage communication and the RTC event can be a good opportunity for everyone to speak with testing specialists across continents and make friends.

With more than 600 attendees expected this year, you can have excellent networking opportunities and gain visibility on what the others are working with.

#2 Unconf

Also, in 2019 we’re introducing Unconf, where you get the chance to have the ultimate “backstage experience” and be the one who drives the conversation.

Remember telling you about our belief in communication?

Oh well, at Unconf you have the spotlight. This workshop will take you on a journey, figuratively and literally, to help you understand how you can overcome your fears of sharing that story, experience, or idea with others.

#3 Top Notch Topics

Among all these, we’re discussing about  test automation, exploratory testing, web security, visual testing, blockchain, testing in AI, leadership and how to manage crisis situations and these are just a few of the topics we are preparing for 2019 edition.

#4 5 keynotes, 8 Workshops, 12 tutorials

In 2019, Romanian Testing Conference comes up with a big variety of workshops and tutorials. Attending one of these, puts you in the same room with industry leaders and gives you the chance to learn from them new skills, new techniques, new ways of thinking, gain proficiency and become better at solving various situations.

Oh, did I mention about having fun? 🙂

#5 Diversity

We fight for gender equality and diversity in our event that’s why our stage has no gender nor colour.

What’s more beautiful than having such an equilibrium between females and males participants: 👩‍💻👨‍💻44.3% females and 55.7% males?

A good measurement on how successful your event is, is to analyse the participant’s returning rate.

We are proud to have 48% rate of returning participants! So, if you plan to see your old friends testers, now is your time.

Did I say five reasons? Oh, there’s actually one more.

#6 Connected Events

We love to create new challenges and take each year a step forward and be better than we were the previous year. At RTC we keep the fire of curiosity, innovation and creativity always burning, that’s why each year we’re creating new concepts around our main event.

If in 2018 we introduced the XTesthaton, a unique concept in the testing community, which combines testing skills and unconventional situations, in 2019 Unconf is introduced. Also, before the main event in June, every two months we’re organising the RTC Meetup, where we are bringing the testing community together, share ideas and knowledge and offering a stage for new voices.

Is an event considered to be successful without the after party, some cocktails and good mood? We have it this year too! In the conference day, when the curtain falls, every participant is invited to the after party to continue chatting and enjoying a more relaxed atmosphere.

Hope to see you in June!

Enthusiast software tester, documentary lover, crazy cat lady, big fan of user experience. Her super power is to watch tennis matches all day long.

14 Most Common Mistakes A Tester Makes

Did you do any mistake recently?

I did.

But we’re all humans, right? And we’re all likely to make mistakes. Usually people associate making mistakes with punishment which in most of the cases is the immediate action after a mistake is made. And seeing the good part in it is almost impossible, at least while you’re struggling to repair what you did wrong.

Making mistakes can have a positive impact on your professional growth, the only condition is to learn a lesson from the mistakes you’re doing. And during the learning process is almost impossible to avoid making mistakes.

Making mistakes is a lot better than not doing anything. — Billie Joe Armstrong

There is no activity domain in which you’re more likely exposed in making mistakes than in others. Below is a list of mistakes a software tester is exposed to during his/her work lifetime and from which can learn several lessons.

1. Incorrectly evaluate the risks

The job of a tester rely much on identifying and risk mitigation. A good risk analysis can help in identifying what can go wrong with the product you’re testing before it goes to production.

Identifying the areas of concern can massively reduce the costs and time spent afterwards in fixing problems found in later stages of development.

Photo by Caroline Hernandez on Unsplash

2. Miscommunicate the impact

Miscommunication is always a mistake, even we’re talking about miscommunicate the impact of a bug, the presence of it or any situation that might jeopardise the quality of the product we are testing.

3. Ignore a bug when you see it

Ignoring things like miscommunicate them should never happen. As testers we must address any situation we’re facing — even if we don’t have solutions for these situations or maybe don’t have the bigger picture, it’s better to make them known than to act like the elephant is not in the room.

4. Using the same test data — pesticide paradox

Executing our testing scenarios using the same test date might lead us to the pesticide paradox. Repeating over and over the same test cases with the same test data will no longer find new bugs.

5. Not keeping test cases up to date

If you want your test cases to be useful, keep them up to date. Outdated test cases don’t bring any value into your testing.

6. Criticising developers

A constructive way of giving feedback and a positive communication can make the difference in a tester-developer relation. Try to spot also the good work a developer is doing, not only the bugs or problems found in his/her code. Add positivity into your testing!

7. Making assumptions

As a tester you should never make assumptions! The best way is to ask all the questions you need an answer for, helping you to understand the requirements, what need to be tested, what was implemented or how the application under test is expected to behave.

8. Incorrectly evaluate and measure the effort

Project Manager: “How much would it take you to test this?”

Tester: “Hm, a couple of hours, maybe?!”

Be sure you make a step back and you see the bigger picture before you give estimates.

9. Frequently changing the focus

Emails, meetings, regression testing, test case creation, test case execution, a phone ringing, a person asking something, a patch in production that needs to be tested, another hot fix. I think you all recognise the scenario.

This can have a negative impact on your productivity and quality of your work. I would suggest you to try to find what works best for you and organise your working day accordingly.

10. Copying the acceptance criteria into the test cases

We are sometimes tempted to make this mistake while writing our test cases when we don’t see much value in writing and executing them. Let’s try not just state the obvious from acceptance criteria in our test cases, but also focus on negative testing, edge cases or other scenarios that might make our testing more complete.

11. Incorrectly evaluate the impact of a new functionality/fix

This is translated by one word: regression. It is crucial to understand what other areas are affected by a newly developed functionality or by a code fix.

12. Being scared of using tools

This might happen when you, as tester don’t feel very comfortable with your technical skills. It’s totally fine not to be a super hero in using tools, but I encourage you to be open to any solution that might ease your daily work.

Even you don’t feel comfortable in using tools, you might get help from other testers, developers or maybe online support.

Photo by Todd Quackenbush on Unsplash

13. Not thinking as the end user

It is better to take the user’s hat and imagine how s/he will use the application you’re testing. It is said that the end user is the best tester which finds more and critical bugs. And we don’t want that, right?

14. Not asking developer’s help

Sometimes we are afraid of being judged or afraid of looking stupid which leads us in trying to find solutions to our problems by our own. It is not a bad thing to be a problem solver. This is not the best practice though when you invest time in doing it instead of asking a developer what you’re trying to figure out.

I encourage you to have a good relation with the developers you’re working and maintain a positive communication. There should be no me vs. you, tester vs. developer kind of situations.


If you found yourself in most of the above situations, I can feel your pain, I went though all of them too through my career. Definitely is desirable to avoid all these mistakes when possible, but when they happen, don’t punish yourself too much. Is good to make mistakes and learn good things from them. Turn your mistakes in valuable life lessons!

Enthusiast software tester, documentary lover, crazy cat lady, big fan of user experience. Her super power is to watch tennis matches all day long.