these are the prerequisite conditions associated with the event handler of type onstarttestcase
so in fact, if the execution model you've defined within your jenkins pipeline does not fit those conditions, the event handlers will not get triggered.
for instance, if you've used the filter of /Project:ProjectName to specify a specific project to run via Jenkins pipeline (and the items within your project's execution plan are marked as a test item) the event handler should be triggered.
additionally, if you have script routines that are associated with BDD feature files, and the feature file OR scenarios have been tagged, these tagged items can be run as a test item (by right click running run tag @exampleTag ) which should also trigger the event handler. Ordinary tags embedded within KDT's will not get considered as a valid prerequisite to trigger the event handlers.
if those conditions are not met, the event handlers will not trigger. if you see that those conditions are being met AND the event handlers are not getting triggered, please submit a support ticket.
- similar prerequisite conditions apply to all other types of event handlers. view the list here
Hi Justin,
Thank you for replying!
We are using below syntax when calling tests in pipeline. Our tests are categorized under different tags and we have different Jenkins job for each tag.
/ProjectPath:"{abs_path_old}/{project_path}" /project:"{project_name}" /tags:"{tags}
Let me know if we need to modify the filter to ensure OnStartTestCase handler is getting triggered.
Thanks,
Pankhuri
