It depends on whether your company provides an efficient way to submit information about payloads and outcomes. For example, if you can submit in a simple, high

It depends on whether your company provides an efficient way to submit information about payloads and outcomes. For example, if you can submit in a simple, high-level structure that's independent of the language used by the test engine, e.g., Payload: EICAR Anti-Virus Test File Endpoint: POST /new-customer Outcome: server file \Quarantine\customer.db exists and \Data\customer.db does not exist Expected: server file \Data\customer.db exists and \Quarantine\customer.db does not exist then it's probably worth the effort of a QA engineer to submit that. However, if you spend only 10% of your time on a project where integration tests must be written in JavaScript and committed to a repo, and there's no way to commit until the new piece of integration test code fully complies with the Airbnb JavaScript Style Guide, then it's probably not worth the effort of a QA engineer. The tests should be committed by someone who works with the nuances of the testing framework every day.