Why we need test automators/quality engineers
Good isn’t good enough for our test automators. They contribute to developing high-quality software by designing demanding software tests. They have an unerring sense of stumbling blocks and special cases and do not rely solely on unit tests and manual tests. Instead, they optimize our quality management with fully automatic test cases on the highest level.
As a test automator, you won’t leave anything to chance.
Employees in test automation, also called Quality Engineers or Quality Assurance Engineers, ensure quality management that’s right and ensure that our product Cadenza is put through all its paces - traceably, reliably, and with the highest quality testing. Test automators examine our software from all angles, think along with application cases, and build suitable test environments.
What distinguishes our test automators
- You have a very good technical understanding, routinely use sample processes, and create automated scripts using state-of-the-art methods.
- Our test automators use tools such as Selenium and JMeter to build test infrastructures and QS plans and write complex, automated tests for front and back end. In the process, they rely on agile test and QM processes.
- They like to discuss code design decisions and are always seeking ways to get the best from the software.
- Communication with the development team is part of their everyday lives, that’s why they are constantly exchanging ideas and information with our developers.
- Testing alone is not enough for them: They also work as part of a team to develop the quality assurance process and they like to work with other teams as well.
How our Quality Assurance Engineers work
Test automators at Disy manage quality assurance, execute it, and also implement new features. They implement interface and load tests with Selenium, retest, and JMeter, and similar tools, sometimes alone and sometimes as part of a team. They know their way around agile frameworks and regression testing, plus Java, JUnit, and SQL. In addition to the actual tests, they are constantly searching for possibilities to sensibly automate manual tests.
Designing quality assurance and the entire QA process is the core task area of our test automators, from design to conducting of the tests in close cooperation with the project team.
What our employees say about the job
"First of all, I check the status of the browser tests run in the central build system. The tests are done automatically in the morning after the autodeploy phase of the nightly build. If I notice anything in particular, I expand the tests and their framework with my development environment IntelliJ. In the background, the local docker containers help me test code changes directly.
After some programming work, I participate in the kick-off meeting for a new project. Here I can get a picture of the project content and get to know the participants. Then I coordinate with a colleague from development; he has eliminated an error and asks me to check the correct behavior of the application. After that, there's a status meeting about the ongoing release tests. We discuss the current state of test progress and plan the next steps.
Next, we discuss how we can better exploit the synergies between the various departments in order to complete the tests promptly before the bug fixing phase. After the creative discussions, I focus on the technical set-up of the communication between the automation jobs of the build system and the test management system. I am able to take a step forward here and document the functioning configuration in Confluence. "