Skip to main content

Friends of good software aka Frogs unconference

Attended a week ago the Frogs (friends of good software) online unconference https://frogsconf.nl/.

Unconference type of events are these days pretty much the only type of conference I wish to participate. They almost automatically establish what many more traditional desperately try - discussions and interactivity.

Frogs was no exception, and was also extremely well organized.

It followed a typical unconference/openspace format, of creating the content and schedule of the conference in the beginning, and then people attending the ones they find most interesting. The conference organizers have background in testing/qa type of work, which is why there where a lot of testing minded people attending, but happily there were also a lot of people from different backgrounds. 

We were using Welo as the platform for the unconference and it worked well, allowing you to move virtually between rooms and hangaround places. Depending on the timeslot, there were 3-5 topics happening at the same time. 

I usually pick the topics where there are least people, because that often makes the sessions more conversational and also you get to know the people on the sessions. So my picks for the day ended up being:

- Getting whole dev team involved in e2e test automation (my own pitch)

- Designing reward systems and incentives for teams/orgs that practice co-creation

- Workshop: Playing around with Playwright

- What is my job if I can’t do any testing, choosing not to have access to system under test?

- Embrace failure; revisiting Boehm’s curve in a DevOps world

Very interesting discussions with great people, laving with lots of ideas and spark for next few weeks of work :)

The next Frogs unconference one is gonna happen somewhere in February I heard, and I am definitely going to join it. And waaarmly recommend the same for everyone else.

Frogs unconference - 12 points! 

Comments

Post a Comment

Popular posts from this blog

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...
3 comments
Read more

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.
3 comments
Read more

Six reasons why testers should do code reviews

I have had quite a lot of discussions about code reviews. Quite many also with testers, by which I have understood that many do not do those. I will not start arguing here on whether code reviews are good/important or not. But I will list a few things why I think testers would benefit of doing them. 1. Code is the only documentation that is up to date . If you really want to know how something really functions, you want to be able to see and read the code. 2. Knowing more about the thing done enables you to do better testing . You can spot things that you should definitely test, and things that you probably don't need to test that much. Like extra things added by coder, usage&modifications of existing functions, data types, etc. And to arguments thinking that one loses their "independence" as a tester by knowing too much, I would worry a lot less about that than about testing stuff that you have no idea on how it has been built. 3. Improve logging . I obse...
2 comments
Read more