Test Manager, Test Analyst, Test Automation Engineer

Project in the automotive industry. I’m running a follow-up project in parallel to the previous one. I work as test manager, analyst, and automation engineer for two teams. Both teams work on the same product, split into backend and frontend. The product is part of a large project involving the biggest German car manufacturers and the Ministry of Economics. The plan is to build a system for full traceability of car parts, from raw materials to the final product, including manufacturers and suppliers. This will be done with a web portal and connected apps.

Given the number of apps and participating companies, the data landscape is huge and processes are complex. It’s essential to make both backend and frontend highly functional for large data volumes and resilient to deviations, while delivering required features according to specs.

To ensure this for both teams, my main tasks are to guarantee quality through effective testing. Besides manual exploratory testing, I design and develop Tavern tests for fast backend regression runs. For extensive integration tests in backend and frontend, I create Cucumber scenarios in JIRA, which developers then implement. I’m also responsible for creating, running, and documenting test tickets, test plans, and run tickets.

Regular reporting, filing bug tickets, and both team-internal and project-wide communication with all involved companies are core tasks, as is attending SCRUM meetings for both teams, supporting and QA-representing team products in cross-team E2E test phases, meetings, and presentations.

Project language is English.

• Managing two teams as Test Manager
• Designing and executing manual tests
• Designing, implementing, and running automated Cucumber and Tavern tests
• Creating and maintaining test plans
• Preparing and presenting run results at iteration reviews
• Reviewing requirement tickets and documentation
• Tavern testing with Python
• IntelliJ with Cucumber
• Gherkin in JIRA
• Various tools for handling JSON, XML, CSV, and HTML
• Insomnia for API calls

Project in the music industry. A neighboring rights company launched a project to introduce computer-based data processing and a related website.

As a test analyst, I first designed test strategies with manual UI and system tests. Then I created and organized test plans and cases, executed them, and documented results. The project included dozens of data processing services and a data capture website, and later added a CRM extension as a test object.

Later in the project, as Test Manager, I coordinated the QA team’s operational tasks and presented QA progress to stakeholders. When the project moved to the next development phase, I trained the business team in new processes and helped plan and execute acceptance tests.

• Creating and maintaining test cases
• Documenting functionality of developed services
• Writing test concepts in Confluence
• Prioritizing and splitting test plans in JIRA
• Designing layouts for test cases and bug reports in JIRA
• Preparing test data and scripts with Postman
• Documenting bugs and helping developers fix them
• Acting as communication link between business and development teams
• Test management and leading QA team
• Confluence
• JIRA
• Xray
• Postman
• DBeaver

Project in publishing. As part of digitalization, the client highly prioritized automating tests for an in-house web application. The goal was to show the benefits of automated tests. My task was to run manual tests, add new ones, identify scenarios for automated regression tests, and develop them in Ranorex.

The test object was a web-based learning platform with interactive exercises for kids. To ensure error-free operation on common browsers and OS, I identified relevant combos, created sensible sets, and presented them to the team. We also evaluated selected tools for suitability.

• Reviewing existing tests for relevance
• Creating and extending manual test cases
• Developing automated UI tests with Ranorex
• Managing tests with Testbench
• Executing manual and automated tests
• Documenting bugs and working with developers to fix them
• Documenting tool selection decisions and reasons
• Ranorex
• Imbus Testbench
• IntelliJ
• Webmate

Project in navigation and automotive. A navigation software was ordered to run on the client’s hardware, so compatibility with all hardware components was crucial. In an international team across three sites, we tested the software in a simulator and directly in vehicles.

Besides test drives, my main focus was QA on the simulator. This allowed broad coverage of traffic situations and reactions of navigation components. We used in-house programs to simulate routes, traffic density, roadblocks, weather, and other navigation scenarios. After creating test plans and data, I executed and documented tests.

Test cases were first run manually, then recorded and used as automated regression tests after each deployment.

• Designing, maintaining, and prioritizing test cases in JIRA
• Analyzing new requirements for potential error states
• Creating test scenarios and data for automated tests
• Documenting and presenting results to stakeholders
• Training new testers in the development process
• Writing test guides for new testers in Confluence
• Documenting and retesting bugs
• JIRA
• HP ALM
• Confluence
• SN3K
• ChromaMap
• ReferenceRouteTester
• TrafficGenerator