How are Selenium automation tests actually setup to run in company following an agile software process?

Question

I have just started learning about test automation in Selenium and found out that most online tutorials would tell you to run the test suite inside an IDE together with a test framework such as TestNG (with testng.xml) and a build tool such as Maven.

When you are working in a software company and told to build a test framework and run automated tests, I don't believe you actually need to fire up your IDE every time you want to execute your test suite. So, my question is, what is the typical setup a software company follows to 'automate' running your test automation scripts?

Answer 1

Software companies are following agile practices and wanna keep up with industry practices. In real projects, CI & CD are used to continuously integrate, deploy and test the software.

Tests are written by SDET using test automation frameworks. While developing test scripts test developers use IDEs like eclipse. However, tests are executed over Jenkins as a job, after required frequency/event.

For example, after every code deployment, Jenkins can automatically trigger your sanity suite, and run regression bi-weekly.

The process' are automated now-a-days with stakeholders demanding agility.

One can invoke selenium java project from command line via .bat file in Jenkins, or using ant/maven as build tools.

IDEs are seldom used to run tests in real world.