Category Archives: testival

What I learned at Testival #32 meetup

Reading Time: 2 minutes

TL;DR

This post is about my  Testival #32 meetup learning experience.

Sponsor of this meetup was Degordian, digital agency  where there is no cure for their curiosity 🙂

They recently moved to new location, and this was my first experience of “Apple” style working place. And it was great experience. When looking such premises only through photos, it may give impression of show off.  But every detail in this place is made with reason. The reason is to stimulate your brain for new ideas and new learning experience! Great job!

 

We started with usual introduction of 14 attendants. One newcomer felt like she does not belong there, because of her educational background. But this was good thing, because we had at the meetup several people with diverse educational background. Software testing is not confirming that stream of binary code works/does not work.

Testing is a “meta” activity. It’s not just a task, but a task that generates new tasks (by finding bugs that should be fixed or finding new risks that must be examined). It’s a task that can never be “completed” yet must get “done.” [James Bach]
Testing is an investigation based on, concerned with, or verifiable by observation or experience conducted to provide stakeholders with information about the quality of the product or service under test. [Cem Kaner]

Marko Kruljac from Degordian presented “Integrating Jenkins with your GitHub Pull Request Workflow”.

Marko talks about Jenkins/github workflow.

 

As I have done similar for several clients, I was curious how they cope with that, because Jenkins offers several options through its great Plugin community.

I learned that for github the best option is Github pull request builder. It also made me think how important is to select Jenkins plugin name in order to present what is actually do.

After pizza and beer break, we had three lighting talks.

Zeljko Filipin from Wikimedia presented unicode zero-width non-joiner character. In Ruby interactive console he merged two “emoji” with that character in order to make new one (e.g. man + pan = cook).

Next day I found that with that character you can make very scary things, like publish your own What’s App application in Google play. Read more about that in Gojko Adzic excellent blog post.

Second lighting talk was from Vilim Stubičan from Degordian talked about his learning process (while he was solving Rubik cube with one hand 🙂 ).

I presented the most important software tester tool, a notebook. Read again James and Cem definitions of software testing to know the reason for that fact.

P.S.

During the testing session in preview mode of this post, I found important issue with one photo because it contained Degordian wifi password. Which automation would caught that issue?

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Testival 2017 second day report

Reading Time: 2 minutes

TL;DR

This post is about opening keynote and open sessions that I attended.

We gathered 40 software testers, which is 20% increase! Alex Rodionov open keynote was about Testers Anxiety. Which was hit to bulls eye because every software tester experienced that.

Software testers usually first spot contradictions in the product which makes them alert and that leads to Anxiety. Alex stated how can you identify that you are lousy tester, if there are bugs in product that you missed. Very simple. I like statement that programming is analysis decomposition, and software testing is composition analysis. Testing is like art. In testing, you should never stop looking for answers.

Then Alex switched to automation in software testing. He mentioned testing pyramid and asked question do we automate too much/enough? Do we trust our automation checks? Software testing is less deterministics and involves many checks, while in automation there is only one check. Then he explained model based testing that is smarter way to do automation.

My first session was proposed by me: What is exploratory testing?  Exploratory testing is so much overused that almost become buzzword. I realized that I can not explain what is exploratory testing. So I started making wiki notes based on this excellent blog post: Exploratory testing pathway by the Marcel Gehlen. I explained to the group what I have learned so far about Exploratory testing. In that way, I expanded that understanding (by teaching others, you also learn).

Second session was about software testing tools that we use in daily jobs and issue that we had by using those tools. I learned about Web Shaper and Charles proxy. Also, Chrome dev tool throttle does not give real results. There was idea proposed by Marko that it would be much better to connect mobile devices to “shitty router”.

During the lighting talks I presented Black Box Testing Machines that could be found in this excellent blog post by Katrina the tester. Post presents various games and puzzles that are used in teaching the software testing.

Zeljko presented Scratch, Vim, and why you should not go to the conferences.

Marko presented impressive set of Jenkins jobs and created on the fly new testing environment by clicking one job!

In UX testing session, discussion whent to the direction which tools are used for user behaviour analysis.

Last session was about state of the selenium. Selenium team will no longer support Browser drivers, that is now vendor responsibility. Selenium conf and Watir Bazar are excellent conferences and if you want to write maintainable browser automatization in Ruby, you should read Cucumber and Cheese book.

In closing session we shared our AHA moment and gave away a set of Test Sphere cards!

That was it! See you next year at Testival 2017!

 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Testival 2017 first day report

Reading Time: 1 minute

TL:DR

TL;DR means too lazy to read (I got several inquires about that).

For contet of this blog post, Nova Runda is responsible party. This post is about first day on Testival 2017, free testing conference.

We had 33 participants, of which there where 12 influenced female testers. We have never emphasized problem of gendered diversity in software testing, but with honest approach  what is software testing, we attracted that number of female software testers.

What I like about Testival is that we have returning participants, and they brought new software testers. along So, open space event approach is good direction.

We started with introductions and proposals for open event slots. And guess what, no hesitation, no need that old Testival testers to start posting their proposals:

“Zeljko, we need to arrange those proposals according to number of votes” I asked. No need for that, participants done this by them selfs, they even created new rooms!:

 

We are starting tomorrow at 9.00 am with Alex Rodionov opening keynote. See you there.

 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

It is Testival 2017 time!

Reading Time: 2 minutes

TL;DR

In this post I announce a software tester event, Testival 2017.

Testival is one day software testing gathering in unconference format:

""Typically at an unconference, the agenda is created by the attendees at the beginning of the meeting. Anyone who wants to initiate a discussion on a topic can claim a time and a space. Unconferences typically feature open discussions rather than having a single speaker at the front of the room giving a talk, although any format is permitted. This form of conference is particularly useful when the attendees generally have a high level of expertise or knowledge in the field the conference convenes to discuss."""[Wikipedia]

Why is for me this format better than regular conference?

As tester I ask a lot of questions, which is not possible at regular conference. Here is scenario: after the speaking slot, there is usually questions time slot, up to 15 minutes. This is time for the whole audience to ask questions. When this time is up, moderator usually announce that you can ask speaker more questions. But speaker is usually  followed by “groupies”, family or conference friends. It is very crowded and noisy, and usually I lost my question momentum force.

On unconference, there is no one-way-speaking part. Topic author gives introduction and initial questions/thoughts. And then discussion emerges. If it is not for you, use the power of two feet and move to another discussion topic (another room).

As an example, after the TestBash Brighton 2017 there was Open Space event. At the end of this event, I had fruitful discussion with Paul Holland and other participants about testing heuristics. He teaches Rapid Software testing and software testing heuristics are part of that class.

Bottom line is that in unconference format you are in control of discussions and you have a chance to shot much more questions!

Testival 2017 is in two weeks in lovely Zadar, Croatia.

We are starting on 1st of September, Friday at 18.00 by proposing discussion topics. Next day, on Saturday, we will execute those discussions divided into slots and across different rooms. Prior those discussions, we will have opening keynote by Alex Rodionov, one of the Watir contributors!

Location is Zadar innovation center. You can apply using this form and admission is free.

All relevant information could be found on conference page: www.testival.eu.

See you in Zadar!

 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

What I learned at Testival #30: learning by playing card games

Reading Time: 2 minutes

TL;DR

This post is about hands on session for learning about software testing using card games.

Intro

At TestBash Brighton2017, on Friday conference day, during the Lean Coffee, one lady ask question that you have probably already heard: “How should I motivate my team of testers?”

I suggested card games. Another participant immediately dismissed me: “I DO NOT LIKE GAMES IN SOFTWARE TESTING BECAUSE THIS IS NOT PROFESSIONAL!”

Noticed that this was his subjective opinion and he did not provide any arguments why is this bad idea. Well dear fellow software tester, this blog post is to prove you wrong.

Introductions

As usually, we started with 2-5 minute introductions. Every tester must be good at explaining things, so this is good way to practice that craft. We had new participants, 3 of them international. Meetup .com is powerful platform.

In this video extract, Priamo explains one concept from excellent book: “The design of everyday things

TestSphere by Ministry of testing

TestSphere is deck of cards about testing concepts, 100 cards divided in 5 dimensions:

  • Heuristics: Possible ways of tackling a problem.
  • Techniques: Clever activities we use in our testing to find possible problems.
  • Feelings: Every feeling that was triggered by your testing should be handled as a fact.
  • Quality Aspects: Possible aspects of your application that may be of interest.
  • Patterns: Patterns in our testing, but also patterns that work against us, while testing such as Biases.

My point of view is that TestSpehere cards can be used for:

  • test plan
  • interview tester
  • share learning

TestSpehere also represents coverage of knowledge that skilfull tester must have. We randomly picked up green cards which represent technique. Each card has:

  • name
  • product level – hint how you should apply this card
  • three examples to seed idea flow

And magic happened! I handed a card to each participant and everybody had something to say about it. Which means we have the knowledge for software testing techniques, and TestShere cards helped us to structure that knowledge.

FluXX

FluXX is card game where rules and goals could be changed on every hand play. You have seven card types:

  • basic rule – draw one, play one. Game initial state
  • new rule – adds rule and removes existing rules if contradicts with them

Hmmm. Are those two rules contradict each other?

  • Goal card – how to win instruction
  • Creeper helps you to lose
  • Keeper helps you to win
  • Action – do something
  • Surprise

Note: play and discard card are two different actions!

How to play? Have one experience player and just play. Start from basic rule, everything else is written on cards (requirements!), but, you will have to think in order to apply them.

Fluxx helps you to practice all types of thinking in fast changing environment.

Game of Set

Helps you to practice multidimensional pattern recognition.

You have four properties: shape, quantity, filling and colour. Each property could have three values. Rule is very simple: you have 12 cards on a table, cards make a set of three if each of four properties are same OR different.

During gameplay I noticed that players usually forgot about one dimension, or they do not take into account that properties could also be DIFFERENT.

Have you ever tested something that has more than four dimensions? Our brain has system one and system two (more about that in Michael Bolton’s Critical thinking for testers.), you need to give system two time to wake up!

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

What I learned on Testival #29 meetup

Reading Time: 2 minutes

TL;DR

This post is about my learning experience on latest Testival meetup.

We had two talks and one 5 minute talk. We started with traditional introduction of every participant. Repsly was again event sponsor.

#1 Zoran Majstorović, ButterflyMX: Ruby Test Suite @ButteflyMX presented Ruby test ecosystem that his company use on daily basis. Those libraries cover whole testing pyramid.  Their web application is developed in Rails framework and they use following ruby gems (libraries):

  • rspec – test runner, automated checks and Rails mocks
  • FactoryGirl – test data
  • capybara – UI automation framework.

Code is on github, and they use branching and pull requests for deploy strategy.  CI system is Semaphore and Code Climate is set of open source Ruby libraries for code analysis.

#2 Marko Filipin, Head brewer and co-founder at Nova runda brewery: A/B testing beer

Nova Runda is one of the first Croatian micro brewery, they are known for their Indiegogo campaign through which they raised money to brew their first commercial beer, APA.

The best beer is one that always taste the same. Striving to that path, they started A/B beer testing. They presented two beers in three cups, A,B,C. They wanted to get statistics how many participants guessed which cups hold same beer. Participants were forbidden to do any commenting while testing the beer (no influence on other participants).

9 of 23 participants noted the difference. The number needs to be 12 so they can claim that they produced same beer in two different batches.

This is known as difference test. Preference test is subjective test. It gives answer which beer is prefered by the tester.

Yes/no test is acceptance test. Is this beer good enough to sell it?

What is beer quality?

  • from batch to batch, beer must taste the same
  • must have attributes of beer type. If you cooked Pale Ale, it must not taste like Indian Pale Ale.
  • ratio of sugar(malts)/bitterness(hops)
  • any not wanted tastes?

Zeljko Filipin presented problems with Vim UX in his 5 minute talk.

As a regular user of Vim, I suggest you to try this ultimate Vim distro. and start with basic tutorial found in Zeljko’s blog post.

 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

What I learned on Testival #28 meetup

Reading Time: 1 minute

TL;DR

This is learning report on Testival #28 meetup that was held today. Our host was again Repsly in HUB385.

There were 15+ participant with three long talks/hands on presentations and four 5 minute lightning talks.

First we had Dario Đurić from Altima. He presented how to create and test web components. I learned that Polymer is Google framework for web components. As any good framework, polymer has out of the box testing support. Polymer enables developer to couple html, css and javascript in components, making your application frontend easier to develop and maintain in TDD manner.

Marko Elezović from Oradian presented how to write concurrent integration tests for api towards the database. Language was Scala, specs was framework for writing tests. Developed testing framework runs tests concurrently. In order to do that, Marko showed us how he resolved issue where every test suites has dedicated postgres database.

Marko Varat, Repsly Inc: presented UX Testing – Product Development Sanity Check.

I learned about tools UXpin, MixPanel and FullStory, tools that help in testing UX aspects of new features.

There were four lighting talks:  Kreso from Repsly explained how Repsly successfully hired senior tester in tough market, Zeljko presented Selenium bindings in Scratch, Zoran from ButterflyMX explained which frameworks they use in order to do TDD in their  Ruby on Rails project. I presented Ministry of Testing TestSphere cards and possibilities how to use them.

 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

What I learned on Testival #27 meetup

Reading Time: 1 minute

TL;DR

This post is report about what I learned at Testival #27 meetup and how I provoked that learning.

Last week we had Testival #27 meetup. Attendant metric was 15/25, which is excellent 0.6! You probably have seen something like this metric in your test reports. 0.6? So what that number means? We recently moved to meetup platform which exposed Testival to local community. 15 testers showed, and 25 applied to meetup. We have total of 65 members in Testival group. This is great improvement for Testival.

Sponsor of this meetup was Repsly, and we met again in HUB385. Repsly is hiring for a QA position. After short introduction of all participants,  we started with lectures and lighting talks.

My takeaways.

  1. Ana showed hers PageObject implementation in javascript. Ruby has PageObject gem with lot of out of the box helpers that you need to develop by yourself in javascript.
  2. Zeljko showed javascript source code for browser automation in various framework. It is less readable than Ruby code and it seems that Ruby gem ecosystem is stronger than one in javascript.
  3. Between two sessions I heard interesting question, how to check large tables using selenium (I always mingle in listening mode in every meetup), and Zeljko mentioned that he successfully used dedicated htl parser for that purpose, not the Watir-webdriver implementation.
  4. I was very impressed how Scratch evolved in past few years.
  5. There is jenkins plugin that enables you to keep history and version of your application builds.
  6. Over beers I learned on real example how is very hard to manage team of programmers. There is no silver bullet, managing a group of programmers is very hard.

Ruby : Javascript in browser automation context 3:0.

Here is small gallery:

 

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Report on Testival #26 meetup

Reading Time: 1 minute

TL;DR

This post is about why we moved from Software Testing Club to Testival meetup group. Main theme of meetup was browser automation.

First of all, I would like to thank Rosie Sherry that have let us to use Software Testing Club meetup group  for Zagreb meetups for six years.

Software Testing Club changed in a good way in this six years. Zeljko and I also did not know the real purpose of meetup, and that is building of local community. Testival meetup group will definitely change that, because now we have free meetup local visibility. As proof of concept, this time we had 20+ attendants, which was much more than usual.

Our host and sponsor was Repsly in HUB385 startup coworking place. Great venue. On meetup, we had two talks.

Kresimir Linke from Replsy had talk: Test Automation of Push notifications using Ranorex.

img_2197

He also demonstrated one complex end to end scenario that involved several users, web browser and two mobile devices. All automated using Ranorex tool.

Second talk was from Ana Prpic: Introduction to WebDriver IO.

img_2200

It is another Javascript implementation of selenium webdriver. Most importantly, Ana presented whole ecosystem of Javascripts tool that enables you to but webdriverIO test in continuos integration pipe.

Meetup was visited by NSoft software testers. They are from Mostar and we discussed with the how to start software tester community in their town.

img_2198

My meetup takeaways:

  • cast device software for presenting mobile device screen
  • how to test email gui
  • html id attribute and security compliance
  • webdrivercss library for visual comparing
  • circleci can run selenium tests in headless mode

After that, Zeljko presented 5 minutes talk format, with his talk:

Why you should not attend testing conferences?

Another talk was about software testing pyramid and I talked about open session conferences (Testival as example.)

img_2201

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather

Report on Testival 2016

Reading Time: 2 minutes

TL;DR

This post is my report on Testival 2016 that was held last weekend in Rijeka STEPRI center.

 

First, a few metrics.

We had in total 32 participants, with female/male ratio 12/20!

As this is free event, dropout count is important metrics for us. 15 registered testers did not show, and did not let us know that they will not show. Which means that we wasted a lot of food.

Testival was first time international event:

Serbia: 4

Hungary: 1

Austria: 2

USA: 1

Liberland: 1

We are very excited about that metric!

Here are links to Facebook photo albums (you need to be log in in Facebook): Irja, Zeljko, Zeljko, Zeljko and me.

Here is my observation. Testers were not shy, they jumped in open session proposals without fear and hesitation:

img_1739

My impression is that several testers problems spawned through all themes.

I got a chance to further model my thinking around idea: “How to kill regression user interface automated testing”, and got excellent feedback and deeper understating of the problem. New material for blog post.

For me, new thing was Splunk product.

And this event introduced for the first time context driven testing school by Ben Simo, that has years of experience of applying context driven principles in his daily work.

Mirjana introduced exploratory testing, and how to transition in daily work from test case step descriptions towards exploratory testing.

My opinion what could be done better for next Testival:

Get proactive help in organising process.

Switch Testival to be Thursday/Friday event.

Add workshops on Thursday day.

More coffee.

Add additional sponsors.

In order to fight against food waste, symbolic price for registration for which value would be given back in form of software testing book or something similar.

Here is audience feedback:

img_1754

 

Again, without our sponsors, this event will not be possible:

screen-shot-2016-09-06-at-9-08-52-pm

Facebooktwittergoogle_plusredditpinterestlinkedinmailby feather