Sunday, January 17, 2016

Introducing FluentLenium (1)

I had started new initiative recently - Facebook group Technology Books. Feel free to join if you look for reading recommendations or want to share your thoughts. Because of that I had to accept hundreds joining requests from many people. (Un)fortunately repetitive tasks quickly bore me, so I figured out it's the perfect opportunity to not only automate it, but also to feature it on this blog. Here is my journey, which now becomes our journey.

Wednesday, January 6, 2016

(In)famous testers

So the new year of blogging have just started. I'm really happy about how things stand at the moment (especially after recent switch to Blogger which cut my maintenance work to minimum).  I'll keep  the same frequency of new posts (1-2 per month) on both blogs. It's good to set goals for new year, and write them down in public, so here they are:

1. Put some extra effort to make technical posts better. I had really nice idea with Ansible overview, but didn't go deep enough. Test detective seems to be doing it much better. At least for now... :)

2. Fix bug on personal www (have you found it already?).

3. Do some SEO/marketing work to make my sites easier to found. Currently I don't advertise outside my social media pages and polish Facebook testing group (which is worth joining btw.) 

I had observed one more thing since I started blogging. My intrinsic motivation level is constantly very high. I read a lot of twitts, blogs and books which help me to keep up with latest IT market trends.

Today I'd like to write few thing things about branding. You probably realised already how crucial your opinion among coworkers is. A lot of times this opinion in influenced by predecessor on the same position. This mean that we (testers/QAs) share and are responsible of the same testing brand in IT. It's in our interest to educate each other, meet, share experiences, etc. 

I'm mentioning this because in the book I currently read - Practices for Scaling Lean & Agile Development polish ISTQB testers have very poor press:
We were giving an introduction to agile development at a client in Poland. Most people appreciated the ideas we introduced but there was an unusually strong resistance from the testers—which puzzled us. At the next-day workshop we had the opportunity to dig deeper into the resistance and found one difference between them and other groups...they were ISTQB-certified testers.
I know there is quite a few testers who are comfortable doing manual regressions only with absolutely no desire to improve their technical skills. Unfortunately managers sooner or later realise that this is 'bottleneck testing'. Let the Yahoo be perfect example how those QA departments end eventually.

In my twitter feed I shared recently nice Kate Falanga presentation '5 Problems In Test … And What We Can Do About Them'. The second problem she identified are bad testers:
Bad actors within our craft depreciating our brand and not helping lack of understanding.
So... are you a tester or a bad actor? :)