The Test engineer develops, implements and optimizes automated tests based on the best testing strategy applicable to the specific change. He or she is also responsible for creating and maintaining test plans and dashboards. The Test engineer further participates in building the team's knowledge base, thinks about future challenges and improvements, and reviews the team's work.
Expectations
All preparation necessary to test stories and features qualitatively before the implementation is complete, to ensure the necessary quality afterwards through the testing itself.
Analyzing and understanding (non-)functional analysis and other input documents
Contribute to the slicing of features and stories in an agile way that is optimal for testing, taking into account sliced coding
Drafting test requirements and scenarios (functional, e2e, regression, etc.) with reusability and scalability in mind
Build and maintain the test framework and test scripts for automated testing, deciding which ones qualify for automated and which for manual testing
Execute the tests with quality as the main goal and the timings of sprints and releases in mind
Log test defects, follow up and ensure efficient collaboration with other team members (analysts, developers) and business profiles to address/resolve the defect as quickly as possible
Describing new or modified (automated) test scenarios based on previous defects, incidents or scope changes
Making your work and progress transparent during sprint ceremonies and showing it during demos to stakeholders
Coaching team members and providing improvements to promote the continuous delivery pipeline
Able to explain complex and technical topics related to automated testing simply and understandably in complex environments with many regulations
Within an agile methodology (Scrum/Safe) actively contribute to the events involved (e.g. dailies, sprint planning, refinement, retro)
Listening to colleagues is something we take for granted. Team players therefore have an edge. And especially team players who work pragmatically, take a positive approach and focus on the essence. Not problems, but solutions. No blabla, but clear language.
However, we do expect some multi-deployability and flexibility. If we need to step in somewhere, we will do so as much as possible, with pleasure. Not everything will be delivered on a silver platter, so taking the initiative, proactivity, transparency and an entrepreneurial attitude are important to us.
Requirements
At least 3 years of experience in manual and automatic testing with a good technical background to be able to read Java code and swaggers for example
Knowledge and experience with Java 17+ reading and writing is a plus (we are currently transitioning from Java 17 to Java 21)
Knowledge and experience with test automation tools such as Postmann, Selenium, Junit are a must
Knowledge and experience with APIs: SOAP and Rest (OpenAPI / Swagger) are a must
Knowledge and experience integrating tests into CI/CD pipelines and products (Github Actions, Jira, Jenkins, SonarQube);
Knowledge and experience with tools such as, IntelliJ, SOAPui, SQL developer, Jenkins, Github Actions are a must
Knowledge and experience with, TestNG, XSD, XML, Swaggers, JSON are a plus
Knowledge and experience in project management tools such as Jira, Zephyr Scale and Confluence are a big plus
Knowledge and experience with middleware is a plus: ActiveMQ, i-PaaS (Boomi);
Certifications such as ISTQB® Certified Tester Foundation Level certification is a plus
