In this post I like to look back at EuroStar Conference 2012. I was lucky this year, because I won a free EuroStar ticket from Software Testing Club! I had to win a contest where we had to invite as many friends as possible. I was happily surprised that they contact ~ME~ in the end. In this post I will write down all those things I remembered the best.
Wednesday, 7th November
Performance Testing of a Road Tolling System by Siegfried Goeschl
I was impressed by how the South-African government wasted so much money. They implemented and tested one of the world largest road tolling system, but never used it (well they use it, but for free). In the end, Siegfried presented a very good case study on how to performance test such massive system.
Testing of Cloud Services; The Approach: From Risks to Test Measures by Kees Blokland and Jeroen Mengerink
Another buzzword this conference was: The Cloud. Polteq had the opportunity to introduce a list with new concerns and risks and show how to mitigate them with tests or test-related measures. In the presentation they shared examples of these concerns and risks. The result was a very interesting presentation with a lot of clear examples.
Why Every System Test Department Should Have a Test Developer (Or Two…) by Kristoffer Nordström
Kristoffer clarified the role description of a Test Developer. He described the skill-set needed to be a Test Developer. Basically you will need both testing and development skills. (It should be someone who can talk with developers and testers). With a Test Developer in your team you have someone who can: do development (for tools), implement test automation, compile open source tools, reproduce complicated bugs and perform non-functional testing. (Looks like my daily tasks :))
Thursday, 8th November
Selenium Over the Years by Simon Stewart
Simon was talking about the history of Selenium back in the days when Web 1.0 ruled the world. He also mentioned all the difficulties we(they) have with different browsers. I remember one of his statements very well:
If you are testing web applications you need to be able to code, if not become a specialist so you can add value in a different area.
I think he’s right, because how can you test something properly, if you have no idea of how it is made.
Testing is Evolving. But Where Is The Evidence? by Andy Glover
Andy works in a highly regulated environment, providing evidence for all the things that are tested is part of his job. Andy explained that recording videos of every test execution is a way of collecting evidence. The advantage is that all the actions performed are recorded. However the disadvantage might be that there is less focus on the side-effects.
Testing the API Behind a Mobile App by Marc van ‘t Veer
Polteq was privileged to supply two tracks at EuroStar Conference. Marc presented a practical case study and explained what the benefits are of having an API behind a mobile App. He also described the additional risks we have to deal with. He emphasized that much more technical skills are needed when you need to test an API.
Test Lab – Coin Game
This time Bart Knaack (Test Lab founder) presented the Coin Game (I think Michael Bolton couldn’t make it). He had two hands full of coins and evaluated each coin. Each coin passed or failed an “unknown criteria. It was up to the delegates to guess the ”unknown” criteria were. The goal of this game was to determine a pattern within a big group of ”data” by asking exploratory questions.
Kalistick they have a tool which can perform run-time code analysis. This means that you can get code coverage insights while executing manual or automated tests.
Telerik they have an App which allows you to do free record-and-playback Web Application testing.