As a test consultant at Polteq I have been sent to Binckbank to inventorize the possibilities of test automation and based on that inventory create an implementation plan to automate any and all tests possible.
Test automation is being done by means of Selenium, Fitnesse and where possible and needed SoapUI.
After acceptance of the implementationplan I have been made responsible for guiding and planning the project leading it to a successful ending together with an automation engineer from Polteq and several testers from within Binck.
Objective is to automate most of the manual, repetitive tests in a sustainable way and teach Binck employees how to ensure the tests indeed remain solid and sustainable.
We created a custom fixture for FitNesse which served as a translation and abstraction layer between FitNesse (the end user) and WebDriver. The custom fixture resulted in all the functional tests being fully human readable, where the code contained no logic at all.
In order to speedup the process of writing testcases in FitNesse I organized a few Testing-dojos. Focus of the first dojo was getting people fully comfortable with writing their logical testcases in a wiki and in a table format and ensuring all tests written get pushed to the FitNesse server in order for them to run continuously.
Focus of the second dojo was to go through questions, unclarities and uncertainties and resolve these impediments in order for the testers to be fully in control of what they are testing and ensuring they see the use of these automated tests.
QA Director at Spil Games B.V.
A relentless ambition, a strategic focus, and an unmatched level of expertise have quickly propelled SPIL GAMES to the forefront of the online casual gaming industry. Today we are shaping the future of online casual gaming.
Our websites and games are carefully targeted to specific demographics, and because they are fully localized into 19 different languages, we are empowered to truly listen to the needs and desires of players around the world.
Starting Januari 2010 I built up a steady QA/Test team with testers located in the Hilversum offices (6 engineers), Poland (1 engineer) and Ukraine (5 engineers). All QA Engineers work within the Scrum teams, as such they are part of the team and share the responsibility of testing stories which have been committed to by the team with the team.
Our work consisted of: testing all underlying services of the SOA base of the Spil Portals, testing all games coming live to site on all Spil portals and all Spil Portals and their respective CMS-es.
Automation works alongside all QA Engineers and thus alongside with all the teams. Focus is on: automating most of the new functionality, all currently existing services, and building out functional monitoring.
During my period at Spil Games we, among others, implemented “social features” across all portals:
- Login/Logout and signup
- Friends, both site specific friends and harvesting friends
- Facebook connect
- User Generated Content
- Complete redesign of one of the portal-groups
- Event system including wall-to-wall-posts, wall posts on highscores, played games, achieved awards and User Generated Content
- Optimizations to speedup the global sites with use of CSS sprites and other technologies
The team works following practices of Rapid Software Testing and Session Testing. Using tools such as “session tester” a log of what has been tested, what was found in terms of issues, bugs and possible other things is saved to the QA wiki blog for reference and in order to keep track of what was tested when and how. Besides this User Stories have a “Test Story” field which should be used (but is not widely used) for explaining what will be tested, how will we test it and what is the expected coverage as well as what will QA need from others in order to make this testing possible.