Parameterizing Jenkins jobs<\/p>\n
If you\u2019re not doing it, or having problems with it read on.<\/p>\n
Design every piece of code in or around your automation framework keeping maintainability, reusability, scalability and robustness in mind (Pillars of framework design)<\/p>\n
In that spirit your Jenkins job should be parameterized<\/p>\n
This will allow you to select different AUT versions, browsers, tests to run from Jenkins itself<\/p>\n
Even if you don\u2019t need it right now, you SHOULD in the future<\/p>\n
In case your automation tool is having problems reading parameters from Jenkins<\/p>\n
You can export them into different file formats (JSON, XML etc.) and read those settings on project initialization of the automation tool<\/p>\n
Easier said than done, but with patience and trial and error, you\u2019ll get there<\/p>\n
#QsDaily #Jenkins<\/p>\n<\/div>