1

Report On Sessions Talks From Vukovar Testival 2018

Reading Time: 3 minutes

TL;DR

This post describes my takeaways and experience about open sessions talks that I attended at Testival 2018. 

Career Development by Zeljko Filipin

Zeljko had proposed this session at other conferences that he attended, so he has a quite remarkable set on notes about this topic. As expected, this session also added valuable data.

First recommendation was ISQTB Foundations book (luckily I was sitting at that time), but getting more information from person that recommended it, I realized that I am not in the position to criticize, because I have not read that book. So my decision was that I should read ISQTB Foundations!

Domain knowledge is also very important, but not only application domain, but also technology domain. For example, if you are testing Android application, learn about Android technology. Read a book, or head to w3schools.com to learn about web building blocks.

BBST Foundations is excellent resource to enhance your testing knowledge and practice. I also recommend book “The Passionate Programmer by Fowler, an excellent resource of recommendations how to become well known professional.

Main takeaway: “You are responsible for you career development!”

You can do following in order to become recognizable by the community:

  • join open source project, code or test it
  • read a book about technology not connected with your current work
  • read/comment blog posts of noticeable professionals
  • share those comments or just blogs that you like/do not agree with
  • prepare a talk and apply to speak at at local meetups
  • attend a job interview once per month or set a long goal, get a 100 rejections at job interviews.

Testing board games by Vilim Stubičan

Vilim had a simple question: If i want to develop a fun board game, how should I test it for fun?

We divided in groups, each group with different game and you joined to group with game that you had never played. We got rules:

  • play game for ten minutes without consulting the rules. Can you reveal the game gameplay?
  • read rules for five minutes
  • play again for five minutes, now armed with rules

I was in Go group. I heard about Go when Google AI defeated best Go human players. Here is my group first take on game:

  • There is a play board with square grid
  • grid consists of vertical and horizontal lines
  • at some intersections are black dots
  • we have black and white chips => we concluded Go is for two players and one of goals is to ‘take’ opponents chips.
  • timeout

We red Go rules:

  • turn based
  • black chips has first turn
  • put chips on line intersections
  • capture the chip (stone), when you put your chips around all four opponent chip neighboring positions (liberties)

We played a game with the goal to eat as much as possible opponents chips. However, experienced Go players explained that main goal is Go is to wan territories, part of board surrounded with your chips in that way, that if opponent puts his stone in your territory, it would be easily captured. 

Other groups played Avalon, Dobble and Jungle Speed.

We concluded that game must have following properties in order to be fun:

  • clarity of written game rules
  • number of players
  • game flow

I recommended book that I read: A Theory Of Fun For Game Design by Koster. That book helped me to understand what makes some games fun for a long time.

Non violent communication by Adina Moldovan

This session was about emotions. We all have emotions and with our actions we trigger emotions in other persons. Simple example is our action that can be request or demand. Demand is ultimatum request, as this must be done. Request if fallible, we expect that it would not be fulfilled. So action taker makes difference between request and demand, not the other side.

Regression Testing by Vilim Stubičar

As I was using my ‘happy feet rule’, I attended only last ten minutes of this session. My experience is that you should transform regression testing into smarter testing. Be smart about it, make it an Session Test Management session of several 90 minutes slots. Use pull request, as developers about changes, consult you application models in order to develop test strategy for you regression test.

This is strategy to transform “blind clicking manual effort” and “long waiting test suite run” into smart and fun activity!   


Also published on Medium.

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Karlo Smid

One Comment

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.