There are 3 teams - Back-End(Java), Front-End(built on AngularJS) and automation testers(Java) teams who are currently work on the project.
For now testers have been writing only system tests for BE.
The time to write e2e tests is coming. Some time ago I was thinking about using Protractor framework for writing e2e test by FE developers.
However, testing team has just proposed them to write e2e test in Java.
Notice: FE team is not familiar with Java, the same for testers regarding JS.
The question:
What do you think how should responsibility be divided between FE devs and testers for developing e2e tests in particular project case and in general?
Hi Derick!
There are 3 teams - Back-End(Java), Front-End(built on AngularJS) and automation testers(Java) teams who are currently work on the project. For now testers have been writing only system tests for BE. The time to write e2e tests is coming. Some time ago I was thinking about using Protractor framework for writing e2e test by FE developers. However, testing team has just proposed them to write e2e test in Java. Notice: FE team is not familiar with Java, the same for testers regarding JS.
The question: What do you think how should responsibility be divided between FE devs and testers for developing e2e tests in particular project case and in general?
Thanks! :)