Januari 2010 – Februari 2011 – Spil Games B.V.

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.

Januari 2006 – December 2009 – eBay Inc. Marktplaats.nl

when: Januari 2006 – Ongoing
roles: QA manager (Marktplaats.nl), Senior QA Engineer (Marktplaats.nl), In Country QA Engineer (eBay.nl)

  • Head of QA for Marktplaats.nl: As Head of Quality Assurance for Marktplaats.nl I have been responsible for extending the QA team into 3 teams: Functional team site, Functional team Admarkt and an Automation team.
    All teams are led by leads in the Netherlands where the teams themselves are located in the Ukraine.
    The QA team in total covers 15 QA Engineers dispersed over 3 different locations. Driving Test Automation to new levels by implementing Selenium Remote Control on a distributed environment with 7 automated test agents wich are responsible for over 50% of regression of the site.
    Driving the quality of work and workpace of the (offshored) QA team to achieve a consistent 80% and higher Bug Detection Percentage.
    Functional test teams are responsible for any new functionality pushed to site in a bi-weekly release schedule with an average of 120+ developer days in new functionalities per release where the Bug Detection Percentage of the Automated tests is steady around 50% and the overall Bug Detection Percentage is consistently above 80%.
    Senior QA Engineer for Marktplaats.nl: As QA engineer for Marktplaats.nl I was solely responsible for making the business aware of the need for testing and quality assurance. Up until 2006 no Quality Assurance or formalized testing was being done with Markptlaats.nl.
    Besides creating awareness and buy-in for Quality Assurance within Marktplaats.nl I worked on testing all projects going live to site, starting with a release cycle of twice a week which, under my guidance, was moved into once a week and then slowly but gradually into one release per two weeks.
  • In my period as Senior QA Engineer I initiated the setting up of a formal test environment with a set of feature pools (e.g. environments for solely testing new features) and 2 staging environments (used solely for regression testing).
    Guided the move away from anthill as bugtracker, upgrading to Atlassian Jira, in which I defined workflows for Bugs, minor projects (2 day projects), Site Operations ticketing and many other uses.
    Together with the test manager at the time we started an initiative for offshoring part of testing to the Ukraine, where we hired 2 testers to begin and later on expanded with one more tester.
  • In-Country QA Engineer for eBay.nl: As ICQA I was responsible for integration testing of all new functionality becoming availabe for eBay.nl site after the test teams in San Jose had tested the features already. Besides manual testing I was working on automated testing for eBay.nl based on an eBay own record/playback tool.