Jenkins parameterisation to run selenium tests

This video will explain
How to use jenkins parameters feature to run selenium maven tests, instead of hard coding the maven parameters
also learn how to use jenkins Active choices plugin to extend the parameterisation.
For more information, visit plugins.jenkin...
Blog - qavalidation.com

[@chaitanyacodelikedude1138]

Very useful, Thanks! please make more on Jenkins

[@shivamohanty6361]

Very informative..Thank you

[@rajaselvapreethasenthilaru7550]

Awesome

[@arvindsharma801]

If we are using parameterization here then what is the purpose of using TestNG in our framework. Shouldn't we do like adding that xml file in our pom.xml which is dedicatedly made for cross browser testing ?

[@qavbox]

Jenkins parameterisation gives more dynamic options to run your tests in different ways / browsers/ environments/ category based on selections, then those parameters we take as mvn command parameters to the framework.
Testng XML is also another way of running tests with different combinations but it's static and you have to add or delete or update the file based on the need which you can avoid with Jenkins parameterisation.

[@arvindsharma801]

@@qavbox I am accepting the point but that is what the Jenkins does continuous integration of the code, so we regularly update our code and Jenkins fetch that code on daily basis if we talk about the real-time production.

[@qavbox]

@@arvindsharma801 I would suggest to not to use testng XML a lot for different scenarios rather than just have the Jenkins/CICD parameterisation and use maven commands in Jenkins itself to accept those values and run the test.
For mvn commands with parameter, refer czcams.com/video/9gAqRurW_PQ/video.html