EWT19 – Domo Arigato, Mr. Roboto

EWT19 – Domo Arigato, Mr. Roboto

Date: 22nd May 2010
Time: 14:30 – 17:30 GMT

Product:: ParkCalc (http://adam.goucher.ca/parkcalc/), using Robot Framework ( http://code.google.com/p/robotframework/ )
Mission:
The airport parking lot calculation tool raised the attention of some managers. There seem to be too many bugs in the application. Since they want to have it re-written, write a regression test suite based on the old application, which may be executed against the new application as well. Assume that the same interface will be kept. Use RobotFramework for your automated tests.
As an oracle for your automated, use the rates mentioned on the official website: http://www.grr.org/ParkingRates.php
We prepared three example tests in RobotFramework that may get you started. Please find these examples at http://www.shino.de/ewt19/ewt19_parkcalc.zip
Please submit your test descriptions (the text files) alongside with any additional resources needed to run them with Robot Framework and the Selenium library installed (that may include code as well) until 4.30pm GMT to http://www.bugrepository.com

Testers: Dhanasekar  S, Anuradha, Anne-Marie Charrett , Maik Nogens, Anna Baik, Tony Bruce, Katya Kameneva, Jaswinder Kaur Nagi, Michael Bolton, Pekka Klärck (lead developer of Robot Framework), Markus Gärtner, Thomas Ponnet.

Markus Gärtner facilitated the discussion afterwards.

Dhanasekar  S started the debrief by giving his report.  He had other commitments today, but on seeing the twitter message decided that he would attend the session.  This meant he needed to download and install during the session.  He felt that he’d learnt a lot during the two hours about this new framework.  He already had prior experience in automation, so realised that automation was not a replacement for manual testing.  He felt that such basic regression tests as we were implementing today really add value to our testing, and quoted Kohl “Test automation is not your goal,test automation helps to achieve your goal”

Anuradha was next.  This was her first time hands on with an automation tool, and she learned a lot about python, and Robot Framework and its testing capabilities during the session.  She was able to install the framework, execute the script successfully, and felt that she’d learned a lot during the process.

Anne-Marie Charrett started by thanking Markus and Pekka and commenting on how much work was done to set this session up.  She had got a lot of confidence from the session as she’d learnt that she knew more than she thought.  By looking at the examples she was able to leverage off what had already been done.  She learnt that sometimes it’s better to plunge and quit – to learn test automation she had to just start writing and be prepared to make mistakes – take baby steps.  Learning a tool like this was was fun, and would be great to build on.

Maik Nogens stated that due to the time pressure, he’d created a new mission for himself – learning about the tool, learning from the discussion of other participants and learning to “stick it out”.  He discovered from the session that test automation has its value, but that it can take a lot of time away from test execution: as you need to understand the code, maintain/change the code, etc.  He had enough test ideas to keep a bunch of automators busy but didn’t have the skill yet himself.

Anna finished the debrief.  She had also focused on learning the tool rather than creating more tests.  She started by looking at the existing tests, comparing them to see what she could build on.  Some great thought-provoking example tests from Markus.  She then decided that before building a new test she needed to be familiar with what a failing test looked like, and started working with the existing tests, changing the data, and thinking about how easy it would be to track down the cause of failing tests.  She felt she had learned a lot from the discussion and issues that other people had raised.

Chat transcript for ewt19

About the Author