Skip to main content
Post Reopened by gnat, CommunityBot, Bart van Ingen Schenau, Izkata, ChrisF
Tried to improve the question for reopening.
Source Link
Doc Brown
  • 220.7k
  • 35
  • 410
  • 625

I am a backend developer and always create tests for my applications. Recently I study and apply the interface tests (using selenium), but I doubted whether I who should create these tests, developer or QA?

AutomatedHow can we decide if automated interface testing areshould be QA responsibility, or Developer responsibility, or both?

And if both, there is thethere a risk of creating duplicate tests?

I am a backend developer and always create tests for my applications. Recently I study and apply the interface tests (using selenium), but I doubted whether I who should create these tests, developer or QA?

Automated interface testing are QA responsibility or Developer?

And if both, there is the risk of creating duplicate tests?

I am a backend developer and always create tests for my applications. Recently I study and apply the interface tests (using selenium), but I doubted whether I who should create these tests, developer or QA?

How can we decide if automated interface testing should be QA responsibility, or Developer responsibility, or both?

And if both, is there a risk of creating duplicate tests?

Post Closed as "Opinion-based" by gnat, Dan Pichelman, CommunityBot, Ampt
edited title
Link
ridermansb
  • 225
  • 2
  • 9

Selenium Whose responsibility is skill for developerit to create the interface and/or acceptance testing? Developer or QA?

Source Link
ridermansb
  • 225
  • 2
  • 9

Selenium is skill for developer or QA?

I am a backend developer and always create tests for my applications. Recently I study and apply the interface tests (using selenium), but I doubted whether I who should create these tests, developer or QA?

Automated interface testing are QA responsibility or Developer?

And if both, there is the risk of creating duplicate tests?