Skip to main content
Software Engineering

Return to Question

Tweeted twitter.com/StackSoftEng/status/1224120455109451779
deleted 6 characters in body
Source Link
sukesh
sukesh
  • 165
  • 6

I'm a C# developer & never worked before on either unit tests or Selenium browser test automation testing.

For a current assignment, there is an existing Visual Studio solution that has a project that does test automation testing. This solution has no unit tests.

For e.g, there is a form on the live site that captures customer data. This Selenium VS project on build, will auto open the browser, fill the form fields with random values, click on submit and verify the next steps like 'Thank you screen', database entries etc. (These test cases are created by developers & not by QC).

This is not unit test, but more of how a QC will test after the development is complete. right?

For someone who never worked on tests before, one advantage I see is, each time the code is deployed to a new environment like STG, UAT, etc, the developer can run this project by changing the URL/connection string, and it will execute all the test cases, saving time and like a regression testing too.

Is this a good approach to use this kind of testing instead of conventional unit tests. If not, what major advantage/disadvantage has one model over the other.

I'm a C# developer & never worked before on either unit tests or Selenium browser automation testing.

For a current assignment, there is an existing Visual Studio solution that has a project that does automation testing. This solution has no unit tests.

For e.g, there is a form on the live site that captures customer data. This Selenium VS project on build, will auto open the browser, fill the form fields with random values, click on submit and verify the next steps like 'Thank you screen', database entries etc. (These test cases are created by developers & not by QC).

This is not unit test, but more of how a QC will test after the development is complete. right?

For someone who never worked on tests before, one advantage I see is, each time the code is deployed to a new environment like STG, UAT, etc, the developer can run this project by changing the URL/connection string, and it will execute all the test cases, saving time and like a regression testing too.

Is this a good approach to use this kind of testing instead of conventional unit tests. If not, what major advantage/disadvantage has one model over the other.

I'm a C# developer & never worked before on either unit tests or Selenium browser test automation.

For a current assignment, there is an existing Visual Studio solution that has a project that does test automation. This solution has no unit tests.

For e.g, there is a form on the live site that captures customer data. This Selenium VS project on build, will auto open the browser, fill the form fields with random values, click on submit and verify the next steps like 'Thank you screen', database entries etc. (These test cases are created by developers & not by QC).

This is not unit test, but more of how a QC will test after the development is complete. right?

For someone who never worked on tests before, one advantage I see is, each time the code is deployed to a new environment like STG, UAT, etc, the developer can run this project by changing the URL/connection string, and it will execute all the test cases, saving time and like a regression testing too.

Is this a good approach to use this kind of testing instead of conventional unit tests. If not, what major advantage/disadvantage has one model over the other.

edited tags
Link
sukesh
sukesh
  • 165
  • 6
Source Link
sukesh
sukesh
  • 165
  • 6

Unit tests vs Automation testing

I'm a C# developer & never worked before on either unit tests or Selenium browser automation testing.

For a current assignment, there is an existing Visual Studio solution that has a project that does automation testing. This solution has no unit tests.

For e.g, there is a form on the live site that captures customer data. This Selenium VS project on build, will auto open the browser, fill the form fields with random values, click on submit and verify the next steps like 'Thank you screen', database entries etc. (These test cases are created by developers & not by QC).

This is not unit test, but more of how a QC will test after the development is complete. right?

For someone who never worked on tests before, one advantage I see is, each time the code is deployed to a new environment like STG, UAT, etc, the developer can run this project by changing the URL/connection string, and it will execute all the test cases, saving time and like a regression testing too.

Is this a good approach to use this kind of testing instead of conventional unit tests. If not, what major advantage/disadvantage has one model over the other.