Test Retreat

Welcome to the homepage of Kris Corbus

Archive for the category “blogs”

Digital Information Units

I start new series of digital information units collection. Pieces I read and found interesting, moving or/and useful for my daily work.

  • Hackers Tactics, Techniques, and Procedures shows some very smart moves. My favourite staging cookies!
  • Blog about “not attacking people with a different understanding of terminology than you”. I like the list of misnomers as a reference that it is OK to be not correct and yes – people should not be attacked, but the same time I disagree with David.
  • Great article about developers bug diary. Do your developers write a bug diary?
  • did you test your back-ups? I remember a conversation with my sysadmin several years ago. update of our issue tracker went wrong and we found out that we do not have a backup. I partly saved the day because I never delete my emails. I offered my help to test the backup after it is set up, but the guy promised that he has it now. Week later system went down again and there were no backups again…
  • tips to organise information – simple but illustrative oracle
  • bringing value or standing in a way? We Latvians have the saying: the way to the hell is made of good intentions.
  • do you want to fail as a consultant? Here is a guideline how.


Naming Conventions

Today I changed the domain of my blog to “Test Retreat”.

From one side – a crazy thing to do, it is just a name and blog has been already linked. All unlinking and relinking… But from the other side, I think a lot about the meaning of things what I do, why I do them and how to name them. The workshop, which I created last month, has something to do with it as well. Because one part of test automation is naming conventions.

How do you name what you create?

I have three kids and we faced dilemma three times to find the names which would sound good in two languages and would fit and work including in two cultures. I think we did a good job and to be sure I just checked it. Positive!

Back to “retreat”. Merriam-Webster offers three definitions for it. With my adaption, this is how I understand and feel it:

  • an act or process of withdrawing especially from what is disagreeable
  • a place of privacy or safety
  •  a period of group withdrawal for study

During my work time I have to follow specific rules and standards and sometimes it happens that decisions are made, which from my point of view are wrong. It can be small things, like “it is a feature, not a bug” or something bigger, like because of lack of understanding customer cuts all testing tasks and adds on top of it “no further discussions about it!!!”. During my working hours, I have to accept that and sometimes even represent as my own opinion, which is especially hard.

My blog is the place where I can escape and write about testing like I understand it, about subjects which are important from my point of view.

This blog is my test retreat.


Comment Challenge

Week ago I observed twitter conversation about commenting on testing blogs. It started with Patrick’s tweet that he read 25 blog posts. Wow! Right? But than Danny asked him, how many comments Patrick wrote. Zero. TwitterI met Patrick few weeks ago, he is really nice guy! But this is not about Patrick, it is about habit. Ask me, how many comment did I leave last weeks? Zero! Why? Mostly I like what I read, it makes me think, it gives me new ideas, new approach for my issues. So why not to prize it, why not to tell it to the author? First excuses what come up in my mind – it takes time and effort. Better to read another blog post, than to think what exactly moved me. Some kind of fast-food reading. Do I want to be fast-food reader?

And than Geir had that idea of 1 comment per week. No matter that commenting idea in testing community is not new, any how it does not stick. Several before tried to kick it off. I get much inspirations from Rosie, but her community challenge last summer I missed out. This year SheyMouse talked about it in his TestBash 99 seconds talk. It is so easy – just one comment in every seven days. So this is it – I challenge myself to comment at least once per week!

Since it was already a week ago, I can report my first results :)

Good that I took that tiny habit workshop few month ago. Few things what I learned there are:

  • it should be light and
  • connected to some action.

Of course I link it with post reading. So now when I am reading, I weight it. If I would comment, what would I write? What exactly I like? What exactly I think I can use in my cases? Last week I commented on three blog posts. They were not the smartest comments, but I am learning and on my way to improve it. Join me! Together we are better.


Found On Internet

Excellent read about developers and some paradoxes Agile Methodology Breast Feeding


Post Navigation