As a software tester, I value collaborating with end-users within the business. This partnership enhances the user experience, accelerates problem resolution, and strengthens communication within agile teams.
As a self-directed software tester, I have been responsible for the following projects and features:
Migration of legacy e-commerce software to a recent version
Establishment of a completely new e-commerce platform
Review and implementation of a new Loyalty program
Review and implementation of a new order processing mechanism
Implementation test automation
Multiple front-end redesigns
Numerous software releases
Creating and resolving issues in product feeds for marketing purposes
Configuring e-commerce software
Configuring scheduling software
Loyalty program: Savings card and points module
Promotions and discounts module
Customer reward module
Order processing and order pick-up module
Reporting module
Review and enhancement of existing modules
HBO Pharmaceutical Business Administration Hogeschool Utrecht
TMap® Suite Test Engineer EXIN
Certified Test Automation Proffesional Foundation Van Haren Certify
Migration of Legacy Platform to Recent Version
In this scenario, the software (content management system application) was years behind the supplier's version and was no longer supported. The challenge was that there were no management, development, or testing teams on the business side, while both old and new versions had to run in parallel. An additional challenge was migrating modules built by an external developer to the newest version. The developer was unwilling to cooperate, and there was no documentation available. As a software tester, I inventoried the processes and the must-haves. Due to time constraints, I maintained continuous contact with stakeholders and suppliers to realize end-to-end tests and risk-based test scenarios, as well as a realistic schedule. I always considered the minimum viable product and the minimal customer journey.
Setting Up a Completely New Platform
Due to time constraints, a direct copy of the existing platform software (content management system application) was initially made, which was then restyled to match the desired brand label. As a software tester and functional administrator, I led the project in its early stages. With a "can-do" mentality, I configured concept versions to get the project running and visualize it. The challenge lay in identifying and assembling stakeholders, owners, and must-haves. Due to frequent changes in stakeholders, the project required a lot of rework and consequently much more testing. An additional challenge was that the software eventually reached its limits in meeting all requirements and wishes. I maintained continuous contact with stakeholders and the supplier to discuss the (im)possibilities and create a realistic schedule. Due to time constraints, the focus was mainly on end-to-end testing and risk-based test scenarios.
Setting Up and Testing a New Loyalty Program Module
There was a need for a completely new custom module where end users could create a loyalty cards and earn reward points. The challenge lay in the many rules and conditions that both the existing software and the new module had to take into account. Some conditions included: purchase history, date, time, price, category, quantity, and type of product. This resulted in a large number of test scenarios. The active and inactive status of the module also had to be considered. As a software tester, I helped clarify the requirements for the supplier who needed to build and maintain the module. I mainly focused on functional testing, risk-based testing, and equivalence partitioning testing.
Setting Up and Testing a New Discount and Pricing Module
There was a need for a completely new custom module where end users could obtain discounts. The challenge lay in the many rules and conditions that both the existing software and the new module had to take into account. Some conditions included: purchase history, content, date, time, price, category, quantity, and type of product. This resulted in an almost infinite number of test scenarios. The active and inactive status of the module also had to be considered. As a software tester, I helped clarify the requirements for the supplier who needed to build and maintain the module. Since it directly involved transactions and internal and external cash flows, I focused on functional testing, end-to-end testing, and regression testing.
Reviewing and Setting Up a New Order Processing Module
There was a need to improve the existing custom module for order processing. The challenge was that the module had been built by an external programmer for the current software (content management system application). The programmer was unwilling to cooperate, and there was no documentation available. The crucial module thus had no management or development team. As a software tester, I inventoried the processes and must-haves. The focus was on status transitions in the software, which each triggered a subsequent action on inventory status, invoicing generation, track-and-trace generation, and requests to the PostNL API. I maintained continuous contact with stakeholders and the supplier to realize end-to-end testing and regression testing. This also took into account hardware components such as local printers, scanners, and networks.
Using Robot Framework, I automate user acceptance tests, functional tests, and REST API tests for web applications on both mobile and desktop platforms with Appium and Selenium. Robot Framework excels in ease of use, readability, and has a large community. An example of an end-to-end customer journey test scenario executed with various libraries at once:
I am a big fan of open-source software like Robot Framework and utilize its available libraries and features optimally. It encourages reusability and integrates with CI/CD tools. What Robot Framework can do for you? Here’s an overview of the use of Appium, Selenium, JSON, and MailClient:
Feature: Checkout
Scenario: Checkout order successful
Given: User is at webapp store
When: User checks out
Then: User finds order at account
And: Store order information
The stored order number and order amount from the previous Appium test are automatically validated in the desktop browser, via the order overview and order detail pages.
The stored order number and order amount from the previous Appium test are automatically revalidated using API GET requests.
The completed order from the previous Appium test triggers the sending of an order confirmation via email. The MailClient library will now automatically validate whether the email has been sent and if the order number in the email matches the order number from the Appium test.
Did you know that Robot Framework also includes a Playwright Library, a Database Library, and an RPA Library? The possibilities are diverse and extensive.
I would be delighted to offer my expertise and discuss the possibilities with you.