“To test, or not to test. That’s the question.” Shakespeare would’ve been able to get away with this but if you dare to say this at Capgemini, there will be a Reinder Otter slapping you in the face. Well ok, that might be a little (just a little) exaggerated but essentially, no project is executed at Capgemini (and actually at every other self-respecting IT company for that matter) without some form of testing. Before one of you awesome developers think you can test it yourself, well guess again. Remember the mistakes you wrote in your paper when you were a student but never noticed till the moment you asked a fellow student to review it? (there should be now some kind of “aha” moment).
- Name: Reinder Otter
- Role: (Acceptance) Test Manager
- Age: 32
- # years working for Capgemini: 4+
- What does an (acceptance) test manager do?: A test manager/coordinator is the one responsible for the test project and knows which test methods are applicable for it. Activities of a TM include maintaining contacts with the project leader and representative(s) of the test team,creating the test plan, coordinating and executing of the test plan, creating the progress report and risk analysis report and advising on the release of the tested system. Other activities may include the filtering of issues from the testers, helping with the creation of manuals, creating templates for test scripts and reports.
- What an average day looks like: Getting up around 6:00 and catch some sleep in the train to the assignment. When arriving just before 8:00, the mail box is likely to be full when the acceptance test is being executed. Filtering all the found issues by the testers, and if applicable mailing them the answer to their questions. Creating and/or executing the test plan by extracting the testing metrics from a self created macro infused excel sheet (used for filtering the “bugs” found by the testers). Informing the project manager and supplier of the software of the found bugs and risks. Helping the project manager with the creation of the manual for the application (not all organizations have a department that does this apparently). A the end of the day on my way back in the train creating a blog post or reading up on tweets and other social media (mostly work related). In the evening working on some internal projects like the creation of the Global Testing & QA community, answering some Capgemini mail and making appointments for (e.g.) the Special Interest Group Test tooling. Around 20:30 it’s time for some mindless CSI and Numbers (kind of like testing…) and off to bed around 23:00…..
- Favorite project/assignment: I guess the best assignment so far was with BuZa (ministry of Foreign Affairs) on the project “Visa application” (NVIS). This was for the ministry a very prestigious project because of the use of new techniques (.NET). During the two years I worked as tester and later as test coordinator, I became somewhat of an “Oracle” and problem solver within the project. This meant that I had to be quick on the uptake and decision making which made it very agile and energetic (which are things I love). Nowadays all the Dutch embassies and consulates all over the world are working with the application, which always gives a good feeling when leaving the project.
- What will be hot in 2009: Agile testing is one of the bigger “risers” in 2009. Although SAP testing and Model Based testing are rising stars as well, Agile will beat them in the end. Why? Mainly because we need it and because Agile development is integrating testing topics more and more. In the current economic climate projects (clients) do not want to invest large amounts of money in order to get a good basis for the future. They want it tested quick and as “lean and mean” as possible. Agile testing is a great way to comply satisfy this demand.
Lee Provoost is a Cloud Computing Strategist and ERP+ lead at Capgemini. You can follow his ongoing stream of thoughts on Twitter http://twitter.com/leeprovoost.