Category Archives: events

Testival 2016 press release

Reading Time: 1 minute

We are proud to announce Testival 2016!

Testival is, simply put, a software testers’ event. A place for software testers to meet with each other and talk about testing. It is a combination of unconference format, where participants selects topics of interest, and keynote speakers.

Testival 2015 was a great success! We had 40 testers and two speakers. Dario Hrupec had talk “How do natural scientist test their ideas” and Maaret Pyhäjärvi talked about “Collaborative exploratory and unit testing”.

This year Testival 2016 will be hosted by STEP RI Science and Technology Park of the University of Rijeka Ltd!

Bookmark your calendars with Testival 2016 dates: September 23rd and 24th 2016!

This year we also have two exciting speakers:

Mirjana Kolarov is Test Department Manager at Levi9 IT Services and she will gave closing keynote: Reaching symbiosis of Exploratory and Automation Testing.

Ben Simo is Amphibious time-traveling context-driven cyborg software tester and he will give opening keynote Putting Context First.

In between is your time, our dear testers. This will be the time for session according to you selection in open session format.

With help of our sponsors, admission is free, and it is mandatory to register through Entrio system.

Our sponsors are:

Screen Shot 2016-07-23 at 3.47.00 PM

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Enter the Dragon

Reading Time: 3 minutes

TLDR

I attended Czech Test conference in Prague from 25. – 26. June. In this post I would like to explain what I learned, what I did not learned, and why I have this analogy in post title.

First of all, if you have any level of ISTQB certificate, you had 20% discount on registration.
Enter the Dragon plot:

“A martial artist agrees to spy on a reclusive crime lord using his invitation to a tournament there as cover.”

This event is highly connected with ISTQB organization. But lets be open minded and provide some facts. I took notes for every session that I attended.

It seems that speaker of opening keynote, Quality control from 0 to 100,  was not prepared to do it. It was much shorter in length, but maybe this is the case because conference start was delayed because of registration issues. Nothing about how to do proper testing was mentioned, but classic ideas from last century such as bug counting metrics or that bug found in production is expensive. There was acronym DDE, defect detected by customer or qa team. My objection to this is that importance of detected issue was not put into equation.

Rethinking QA was presentation of Concur. It was based on heavy automation and CI in order to have feedback loop as short as possible. But feedback was only regarding broken code. They implemented company culture that quality is whole team responsibility, not just of testers.

Presentation about checklist main point was to use checklist in order not to forget something important. And it is important that those checklist are dynamic, and just general guidelines. They must not become general best practices.

Writing effective test cases was about testing ideas. But not as in Context driven school of testing, where every test is an experiment, but how to write instructions for other testers. Pairwise technique was mentioned in order to cope with combination of variables. It was not explained, but that PICT tool (BBST Test design has one exercise with that tool) could be used to implement pairwise testing.

ISTQB news was 20 minute session about ISTQB. Funny thing was that on last year conference, audience feedback was that this session was boring and too long, so they make it just 20 minute. They said that by the end of this year, they expect 400 000 ISTQB certificates (so far in history) to be issued. They announced Glossary site, and as I am not big fan of this organization, I must admit that I acknowledge this site. For example, If I would need to visit client that is ISTQB infected, I would prepare myself using this glossary in order enhance our communication flow.

Panel was missing the audience input. One reason for that was that it was not clearly communicated how to ask questions. 6 ISTQB testers in suits were talking about various topics: tomato technique, procrastination, mind maps, One thing book. It was also mentioned that Wikipedia is not relevant source of facts, which I disagree. It is edited by community, and english version is promptly corrected when not true information pops up.

Performance problems session provided 4 examples from real case how to cope with performance problems of typical web application. It was good presentation.

QE default to open was about open source projects and how to manage it. Also good session.

On this conference I met Mirjana Kolarov, one of the founders of Test’RS club. She held interesting presentation: Test cases and traffic lights, is it a traffic violation? As we were in dragons nest, this was very brave presentation. It drifts towards Contest driven testing by explaining that blindly following test case steps would make us miss important issues.

And in parallel track was Zeljko Filipin How software that runs Wikipedia is tested. I have already seen that presentation, but was enhanced one. It explains testing tools and infrastructure used at

Wikimedia foundations.

Should you visit next Czech test conference? My recommendation is yes, 40% of presentation were good and I learned something from them. Also, I still have not paid for that conference, because I have not received invoice for it.

And I successfully returned from ISTQB nest!

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Welcome to CITCON2014 in Zagreb Croatia!

Reading Time: 1 minute

I am pleased to inform you that registrations to CITCON 2014 are opened today. CITCON stands for Continuos Integration Testing conference. It is actually unconference, and its topics are continuos delivery and practices (continuos integration and testing) that go along with it.  I have already registered and I can assure you that there will be interesting software testing topics to discuss.
Date is September 19 & 20 (Friday and Saturday), 2014. Place is Zagreb, Croatia, my city of residence. Registration is free and limited to 150 attendants. So, do not hesitate to long to register.
Welcome to Zagreb!

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Software tester formal education in Croatia

Reading Time: 3 minutes

I attended Viaqa 12, Croatian software testers conference. Conference topic was ‘Software testers education in Croatia’. As I have been a software tester for twelve years, conference organizers invited me to participate in round table discussion on that topic. Other participants were Zeljko Filipin, owner of the first Croatian software testing start up company and man that has a great experience with testing the web applications, Tomislav Buza via Skype, he writes on his popular blog about his usability testing of various web applications, and dr. Valentina Kirinic from Foi,  professor that teaches students about software testing.
When I finished my formal education in 1997, there was no any subject about software testing at my faculty Fer. Everything that I learned about testing was self learning, and I started to do that when I got a question from one of my colleges from work: ‘Have you ever read any book about software testing?’ So I started with following books:

  • How to Break Software: A Practical Guide to Testing, James Whittaker, 2002
  • Lessons learned in software testing: a context-driven approach, Cem Kaner, James Bach, Bret Pettichord, 2001

Those books were a mind twister for me! They were the root point for gaining the software testing knowledge,  because through the authors twitter connections, I found about other great testers. The important thing is that I practiced the knowledge in my daily work, and based on that I know that I am on a right path.
Thanks to Zeljko, Bret Pettichord attended Viaqa 2011 and I had a great pleasure to met him. After the confernce sessions, we talked over a beer at pub Medvedgrad, and Bret explained to us, actually presented his test report (orally), the great Northeast blackout of 2003. At that moment I comprehended what is software tester. James Bach is a software testing legend, and why is that you can check in his lecture on software testing. His video Steve McQueen Consulting Software Tester, just added more comprehension on what is software tester.   
I attended Rapid Software Testing course, held by Michael Bolton, choosing that course based exclusively on Michael’s writing at his blog. For me Michael’s blog is one of the best blogs, not just from the field of software testing. I don not know how much time does he spend on every blog post, but how he puts his thoughts into the words is just amazing. And those thoughts are the gold for every tester.  
So I was very interested to hear what do professors from Foi teach kids about software testing. I got a clue, based on the software testers education topic discussions form other great testers. So my fear was confirmed, a lot about standardization and maturity models. I asked do they teach them some  practical testing, and the answer was that there are 30 hours of testing practice. They give them assignement to test some web application, based on the some testing standard. No guidance at all. And this is bad. This is the reason why fresh students have fear of software testing.
The good thing is that Foi professors were part of the round table. They listened what others said. They staid to the end of the lighting talks.


We had following lighting talks:

At the end of lighting talk, one student, that is doing his final diploma work about testing education, approached to me and requested some materials. I gave him great presentation from testing conference Lets Test 2012 with title ‘So you think you can test’.


As a conclusion I will state my goal. To bring any of mentioned great testers to speak in front of Foi students about software testing. To show Foi students  how does practical testing looks like at their 30 practical hours of software testing course.   

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather