We have created a customized framework which has only a driver script. We have test set that contains QuickTest_Test (Driver script ) followed by all functional test cases(this approach is required for us to track metrics). The driver when executed will compare the test name against run manager (framework file) for the tests that exists in test set and execute the automated test in back end and attached the execution log file to respective functional test cases in ALM test lab and also updates the execution status. This works perfectly fine in ALM.

When I configure a job in jenkins and run this test set, test executes, but the job never end's. Keeping spinning for ever. As as result I need to kill the job every time. This is not good.