Skip to main content
Software Quality Assurance & Testing

Return to Question

Tweeted twitter.com/StackSQA/status/857806147352395776
Post Reopened by Kate Paulk
Edited to make less opinion-based.
Source Link
Kate Paulk
Kate Paulk
  • 31.5k
  • 8
  • 55
  • 109

Do What reasons would companies combinehave to use web testing (Selenium) and API testing (SoapUI) infor the same projectfunctionality?

Scenario: I want to test a new functionality in the system "login and verification". I assume that developers have done the unit and integration test, and iI am just doing a system test

Do companies (that want to do things right) tend to separate tests for API using one tool (like soapui, that will later let you do performance tests) and then write separate tests in another tool like Selenium for the web interface? Or do people tend to do just the web testing automation because if there is a problem, the tests will show it anyway?

I mean, I understand that it might imply duplication of effort, and I was just wondering if it is worth it and if it is done commercially.

Thanks in advance!I particularly want to know why companies would have both API tests and web tests when this causes duplication of effort.

Do companies combine web testing (Selenium) and API testing (SoapUI) in the same project?

Scenario: I want to test a new functionality in the system "login and verification". I assume that developers have done the unit and integration test, and i am just doing a system test

Do companies (that want to do things right) tend to separate tests for API using one tool (like soapui, that will later let you do performance tests) and then write separate tests in another tool like Selenium for the web interface? Or do people tend to do just the web testing automation because if there is a problem, the tests will show it anyway?

I mean, I understand that it might imply duplication of effort, and I was just wondering if it is worth it and if it is done commercially.

Thanks in advance!

What reasons would companies have to use web testing (Selenium) and API testing (SoapUI) for the same functionality?

Scenario: I want to test a new functionality in the system "login and verification". I assume that developers have done the unit and integration test, and I am just doing a system test

Do companies (that want to do things right) tend to separate tests for API using one tool (like soapui, that will later let you do performance tests) and then write separate tests in another tool like Selenium for the web interface? Or do people tend to do just the web testing automation because if there is a problem, the tests will show it anyway?

I particularly want to know why companies would have both API tests and web tests when this causes duplication of effort.

Post Closed as "Opinion-based" by IAmMilinPatel, Bharat Mane♦, Narendra Chandratre, Michael Durrant, Shailendra Rathore
Source Link
Declamo
Declamo
  • 61
  • 2

Do companies combine web testing (Selenium) and API testing (SoapUI) in the same project?

Scenario: I want to test a new functionality in the system "login and verification". I assume that developers have done the unit and integration test, and i am just doing a system test

Do companies (that want to do things right) tend to separate tests for API using one tool (like soapui, that will later let you do performance tests) and then write separate tests in another tool like Selenium for the web interface? Or do people tend to do just the web testing automation because if there is a problem, the tests will show it anyway?

I mean, I understand that it might imply duplication of effort, and I was just wondering if it is worth it and if it is done commercially.

Thanks in advance!