Testing Accountability & Responsibility

Hi Front-End (Android, iOS, Web) Evangelists!

Traveloka Engineering finally has a formal agreement on the ownership of testing. Currently there's a confusion in who should own UI testing.

Based on discussions with Deri, Denni, Benjamin, Anshul and Lucky, it was agreed that:

Accountability and Responsibility of unit testing belongs to Front-End Engineers.
Accountability and Responsibility of UI testing (with API mocks) belongs to Front-End Engineers.
Accountability and Responsibility of CI/CD pipeline, testing framework and standards (0-1), belongs to respective infra teams.
QA may choose to help, but it's not their obligation.
QA will continue to invest in Calabash based black-box testing.

Please note that the decision to write the tests still lies under product team. Mature products stands to benefit the most with automated testing, while start-up-like products may benefit more from more agility. However should each product team decides to pursue automated testing, who is accountable and responsible for the tests is already clear.

This agreement should give more weight when you are pushing for UI test coverage in your respective platform.

More detailed information can be found in this document: https://docs.google.com/document/d/1ggFE3lhwa9QjWrrlcncwMtvQgIzbK49z4NIZczDugDk/edit?ts=5b447965#

Let me know what you guys think. Don't hesitate in asking questions or raising your concerns! :bow:

Testing Accountability &amp; Responsibility

Testing Accountability & Responsibility