In-vehicle test engineer

Role: In-Vehicle Test Engineer

Location: Burr Ridge, IL (Need to be onsite from day 1)

Duration: Long Term

Responsibilities for KPI and Key-Cycle Testing:

Completing the Key-Cycle Test for every major release build given to Off-Highway Vehicle Product validation team. The Key-Cycle Test is an on-vehicle test that consists of installing hardware and software on a Magnum Tractor and performing 15 individual key-cycles on the vehicle. During each keycycle, the tractor is driven around the test-track and all the system’s functionalities, such as Autoguidance, Tractor App, Coverage Mapping, and ISOBUS, are evaluated. Logs are collected during the entirety of the test and any defects that are found are documented and reported. These 15 key-cycle tests is completed once on each of the following 6 PCM variants: (PCM stands for processing and control module; it is the tractor’s on-board computing module).

• DEV PCM1
• DEV PCM2
• DEV HINOC PCM2
• PROD PCM1
• PROD PCM2
• PROD HINOC PCM2

Results are recorded in an excel doc and analysed after the test is completed.

Completing the KPI (Key Performance Indicator) Test for every major release build given to PS&T PV. The KPI Test is an on-vehicle test that consists of installing hardware and software on a Magnum Tractor and timing how long different menus and features take to load. Each feature’s loading time is measured three times. Logs are collected during the entirety of the test and any defects that are found are documented and reported. This test is completed once on each of the following 6 PCM variants:

• DEV PCM1
• DEV PCM2
• DEV HINOC PCM2
• PROD PCM1
• PROD PCM2
• PROD HINOC PCM2

Results are recorded in an excel doc and analyzed after the test is completed.

Qualifications:

Required Skills and Experience:

• 4 yrs experience of In-Vehicle Testing and capturing logs and analyzing them
• 3 yrs experience in test automation framework, test scripts creation of Mobile App or In-Vehicle Apps with Android and IOS platforms.

Tools:

• Vector CANanlyzer
• CANoe
• Pycharm
• QC/ALM
• Selenium
• Subversion
• JIRA
• Jenkins
• Appium or Robotium or Perfecto.

Experience with:

• Cucumber
• TestNG
• Junit

Methodologies:

• Agile
• Spiral
• Waterfall
• Iterative

Preferred Skills:

• Describe electronic functional testing on prototype vehicle
• Define test requirements for electronic subsystems
• Electronic system diagnosis and corrective action
• Validation of vehicle software using Python Test Scripts on PC Simulator
• Ability to analyze and troubleshoot CAN logs
• Resolution of functional issues, tickets as per CRB priority in Polarion