CITCON 2016 in Cluj-Napoca was the first CITCON I have ever attended and definitely not the last one.
Category: Testing Insights
The Continuous Integration and Testing Conference, abbreviated as CITCON, is an OpenSpace non-profit conference which for ten years has been organized in various cities around the globe. Currently, each year there are four editions taking place on four continents: Europe, America, Asia and Australia & New Zealand. The previous editions in Europe took place in London, Brussels, Amsterdam, Paris, London again, Budapest, Turin, Zagreb, Helsinki and this year in Cluj-Napoca.
Hoping I’ve got your attention by now, I invite you to discover the last part of my retrospective series.
Which was my influence within the project?
My influence on understanding the client’s need to be informed
I learned from my past experiences that even if the client is not specifically asking for a status all the time, he wants to have transparency and he needs to be informed of what is happening.
In the first two parts of my retrospective series I revealed I had the opportunity and experience of traveling a lot to the client’s site.
What about working on client’s site?
Now, this is an interesting topic, because, until this project, I worked mostly remote, in the Altom office.
Working on client’s site was a request I knew about from the beginning of the project and I found it intriguing and challenging at the same time. I was told I should be available at client’s site in Germany as much as possible in the first three months. I knew this would take me out of my comfort zone. No sooner said than done.
In the first part of my retrospective series, I told you about the first three months I spent on the project, the challenges I encountered and the lessons I learned.
What changed after those 3 months?
Well, the Pilot project ended. And the actual collaboration started.
Since the Pilot project went well and the clients were pleased with my involvement, work and qualified opinions, the project was extended. The trips to Germany were carried on as before.
Recently, I finished a project I was involved in for 2 years. I had the opportunity to allocate some time for doing an analysis, so I started to write down my ideas. The outcome was a nice and comprehensive retrospective, covering challenges I encountered during the project and lessons I’ve learned, which I would really like to share with you.
Since we’re talking about a long project and my ideas expanded on lots of pages, I decided to do a series of four blog posts that I’ll post during March.
The series will debut with how I started the project and how the first three months on the project were.
We participated in the first edition of the European Testing Conference and returned with many notes, ideas and impressions which we would like to share with you.
This is the first post in an ETC 2016 series, dedicated to the talks and workshops that we attended.
In 2014 our colleague Ru created a tool in Google Scripts to support her testing in an organized and measurable way, using the Session Based Test Management method. The tool is available in the Google Templates Gallery via this link https://drive.google.com/a/altom.ro/previewtemplate?id=0Aqk-dNwZsfwrdHlfYTRSN3FKQzlVenBYWUhZUk44REE&mode=public&ddrp=1#.
Those bad Bad habits, who doesn’t want to get rid of them?…
Let’s consider the following hypothesis: small habits that slow me down in my work or stand in the way of solving problems could accumulate and have quite an impact on my work. This could mean that they are the silent, unnoticeable factors that influence my testing in a bad way. One such habit may not make a big difference, but when dealing with more, they could have a considerable influence.
I’ve been thinking about how to approach the subject of “Bad habits during testing activities”.
This concept of bad habits was very abstract to me and no bad or good habit came to my mind no matter how much I struggled. Then an idea hit me. How about I put myself in the context of testing something and observe my habits while I test? I may not pass through all the testing activities with this exercise, but it is a good starting point.
I’ll think about the test activities I had yesterday. Let’s see. Yesterday I did pair testing with my colleague Raluca. We were supposed to test a pretty straightforward feature, but the setup to get there was a bit tricky.