Software Qualification and Test Automation Engineer
[ad_1]
Introduction
The sector Development & Engineering within our client, is responsible for the specification and the design of products. In this sector, the department SW DE EUV SWAI & Source specifies, executes and controls the testing and integration of the various EUV software systems into a software release.
Job Mission
Test and qualify the new software versions to provide insight on its quality and whether the versions behave according to their specification. This information will be used as bases for the GO/NOGO advice for the releases.
Job Description
– Test Impact determination: in discussions with architects and developers, the impact of a release or service pack must be determined to be able to select existing testcases or create new testcases. The software qualification and test automation engineer will look at these deliverables from a customer’s point-of-view, and test from that customer’s system perspective.
– Software qualification: define and execute software qualification tests on dev benches (simulated environments) and test benches (partly simulated). As much as possible should be tested on dev and test benches to relieve the claim on the very expensive proto type systems. Be keen on representativity of test environments.
– Software qualification: claim, organize and coordinate test execution on proto and pilot type systems by defining execution plans and discuss these with the machine fathers.
– Support integration by executing test automation on daily bases to gain insight on software patches before integration.
– Creating system tests: create system level test to qualify the system and the software and to test the reliability of the system and the different modules of the system. These system level tests are typically implemented in the form of Python scripts or as keyword driven test scripts.
– Analysis: do the first analysis of the problem to find the development project that is responsible for fixing the problem. After the problem has been dispatched you should assist the development project in defining and testing the solution and make sure that they deliver an adequate solution in time.
– Reporting: clear reporting on issues found, both in an issue database, as well as in overviews and in a test analysis report. Avoid loose ends by status transparency to stakeholders via our qualification progress tool (Jira).
– Continuous improvement: new issues coming from the field or factory must be analyzed why they were not caught in our own tests, and preventive actions must be defined to make sure future testcases will capture these.
[ad_2]
Source link