September 2017

Let’s Talk About Test…

In this blog series we speak to testmanagers and testing coördinators from different branches. At Testersuite we are curious about the different point of views on testing and what keeps a testmanager or testing coordinator busy during a workday. Meet Pascal van den Brink, testcoördinator at HANOS.

Who is Pascal?

I am Pascal van den Brink, 32 years old and I live in Apeldoorn. I am married and I have two daughters. I have been working at HANOS for the last sixteen years, and the last couple of years I have been a testcoördinator for a SAP project.

What can you tell about HANOS?

HANOS is a business food wholesaler. At HANOS, customer satisfaction is paramount and we strive to have the finest and highest quality products. We provide a positive experience for the customers. In addition to a wide range of products, a customer at HANOS can also get advice on a wine that fits perfectly with a dish, or get advice on how to prepare dishes. In addition, we provide luxurious Christmas packages that can also be customised to the customers request.

How did you end up at HANOS?

When I was sixteen I worked a part-time job in the warehouse at HANOS. I had recently finished school and had gotten my diploma in IT. After that I wanted to study logistics and economics. Eventually, I figured out that it was not my forte. I stopped my education and I started to work fulltime at HANOS. I had several functions. From truck driver to order management to logistics employee of Christmas packages. IT continued to hold my interest and I had the opportunity to receive a  position in IT at HANOS. Since then I have been the system administrator for 6 years and eventually switched to the role of functional tester.

“I think it’s important to keep educating your tester. This increases awareness about the importance of testing.”

What is your current role at HANOS?

When I started the SAP implementation at HANOS over three years ago, I was going to fill in the role of test coordinator. It was important that the business itself tested but there had to be some degree of control over the testproject. At this moment we are ready to roll out SAP and we are working on optimising SAP further. The Change Advisory Board (CAB) determines which changes are made in which release.

I am now preparing and coordinating the testing of releases. For this I have made test sets and datasets. Our team consists of four consultants (functional managers) and two ABAP developers. Together (in the CAB) we make the releases. In addition, there are about fifteen people from the business (key users and end users) who perform tests. The consultants focus on particular unittests and exploratory testing, the business testers test in a structured way using the test and data sets.

We have a release every four weeks. The first two weeks we specify the test cases and that are being tested by the consultants and developers. If there are new processes that need to be tested, I take the initiative to sit down with the business team to test these scenarios. I make use of existing test cases as much as possible. The third week is where the business unit tests. If the quality is good enough and there are no more issues, the release goes to production. In the fourth week aftercare is provided and high priority incidents are solved. In addition, we start in the fourth week with preparations for the next release, the functional and technical designs get made.

What does your day look like?

At 6:50 am I am on my bike on my way to work. I am there in five minutes. When I get to the office, I start processing my unopened e-mails. Then I view what changes are ready in TOPdesk for the upcoming release. I put the test that are ready for change into Testersuite. As a test coordinator, I often join project consultation. I also manage the SAP authorisations. I myself test the authorisations, afterwards I let SAP users test and accept the authorisations (the User Acceptance Test).

What challenges do you have as a test coordinator?

My biggest challenge is to get the people from the business unit to, free time for testing and test correctly and concentrated. I aim to make the testers focus on the processes where the risks are the highest.

How do you solve these challenges?

I schedule the tests a coulee of weeks in advance, so that the business testers have the opportunity to make time. This works very well, because from then on it is an appointment. When we get to testing, I prefer to do that in a separate room with them. The business testers prefer not to test in their own work cubicle. This way I make sure that they are concentrated and testing well. I also implore the tester to turn off their cellphones and other digital devices that could cause a break in concentration. This works well. When they sit together, they can communicatie back and forth if something is unclear. For extra support and knowledge, we schedule workshops our testers. Soon, the testers will get the “Structured SAP Testing” workshop from PTWEE. The goal of this workshop is to increase awareness of the importance of testing and to how structure your test perfectly.

You are using Testersuite, how do you put this into the test course?

For every SAP action used by HANOS, testcases have been created. We then combined them into test scenarios. If a release is tested, I will complete the relevant test scenarios and specify which variants to test. The variants are provided to me by the consultants and / or developers. In the test scenarios the ticket numbers are also in TOPdesk. The testers carry out the tests in Testersuite and immediately record the findings in Testersuite. I check the findings and determine which ones need to be addressed by the consultants and developers first. The consultant or developer will resolve this. I will be notified automatically if they are resolved. The business testers retest this and conclude the findings if they are well resolved.

“Working with Testersuite is easy. You can just pick some random person from the street and make them work with Testersuite.”

What is the added value of Testersuite?

As a test coordinator, I’m very pleased to have an excellent tool where I can easily do test preparation and test coordination. With Testersuite it is very easy for me to complete all the tests in the correct order. It helps me structure my test paths. The Masterlist module provides a useful function for managing and using (retrieval) regression test cases and test scenarios. In addition, you can easily find test results and findings in Testersuite. We can check with HANOS if something has been already tested in the past. Another advantage of Testersuite is that it is very easy to use. You can just pick some random person from the street and make them work with Testersuite.

I am pleased that Testersuite informs customer about new features. The changes are described in release notes that we can read in the help documentation. When there are new release notes, you are notified when you log in to Testersuite. I also enjoy the short webinars that explain the new features. I recently followed a webinar which explains the new import function. The import function was something I was initially struggling with. After the demo and explanation in the webinar, I was completely clear on how it works and what the possibilities of import function are. What I also like about Testersuite is that they realise the wishes of a customer. If I look back at how the product started, and how much positive change it has been through it amazes me. HANOS will always use Testersuite.

How do you see the future for you as a test coordinator?

I want to further improve the test sets at HANOS. I strive for better quality, better testing and better testing by the testers themselves. I would also like to see if we can do more tests outside of the happy flows. In addition, I want to investigate the value of automated testing for HANOS and I want to get an Agile degree in 2018. So there are enough challenges for me!

What developments do you see in the test box that are worth mentioning?

Automated testing is the future. The test preparation as it is now will remain, only some actions will be automated. This takes less time. Controls of the test results will also remain manual labor. I see the development of working Agile, also in SAP environments. It’s about bringing short, manageable pieces live, this is definitely the future.

Do you have tips for other test managers?

My first tip is the importance of planning and utilising your calendar. Realise that it’s important to book your people at the moment that they really need to test. I have another tip regarding Testersuite. Take advantage of your Masterlist and keep your test kit up to date. It is important to have a good structure in your products and requirements. This way you can connect your test set and simply select tests for test courses.

Do you have any interesting experiences in testing that you wish to share? Let’s talk!

If you want to be informed about our upcoming blogs, follow us on LinkedIn, Facebook or Twitter.

« back