ApisathS
Occasional Contributor
Joined 4 years ago
User Profile
User Widgets
Contributions
Jenkins (Failed) + TestExecute (Passed)
Hi Everyone, Not sure if anyone ran into this issue before. We have Jenkins set up to run our test script. When Jenkins finished, Jenkins showed as FAILED run but when checking the result. All the executions showing PASSED. Any suggestion if there is a setting within Jenkins that causing this issue by chance?2.2KViews0likes6CommentsRe: TestExecute : store test variable to Project Suite
Hi ebarbera Thank You for taking some of your time to answer these questions. TestComplete is running on my local laptop, but TestExecute is running through Jenkins jobs that have their own dedicated VDI. The code and script are exactly the same, just running on different machines. My coworker and I tried two different Laptops within TestComplete. That's working just fine. Not sure why TestExecute is giving us some hard time storing test data once it's generated from the script. Thanks, Ap1.3KViews0likes5CommentsRe: TestExecute : store test variable to Project Suite
Hi ebarbera, I am not getting any errors, but when the script ran within TestExecute. The test data does not save and store into Project Suite Variable like it should like how it is with TestComplete. Currently, with the same script that was run within TestExecute. It was successfully run, but new data does not store onto Project Variable Hope this helps.1.3KViews0likes9CommentsTestExecute : store test variable to Project Suite
Can TestExecute be able to store new Test Variable onto Project Suite like how TestComplete did? Currently, we have multiple Projects that export data into Project Suite and store those data so that other Projects can reuse the same data. Our TestComplete works nicely with this feature, but somehow TestExecute cannot save/store new data onto TestExecute Project Suite for other projects to reuse them. Any suggestion? Example function logData () { Project.Variable.newData = (data); ProjectSuite.Variable.newData = (data); } This works really well within TestComplete but not TestExecute.