UFT or QTP should not be able to edit, update or save Non Draft ALM automated test cases
Question ID: 109946

In general, if there is an ALM test script that is of the “QuickTest” type in any ALM project, using the external UFT/QTP automated tool we should be connect to that specific ALM project and be able to pull/fetch this automated test script, modify it and save the updated script back to respective ALM project.

When the test script approval process is in place, something like Draft, For Approval, Approved. Ideally, the automatic test scripts which are with Draft approval status should be able to be pulled & modified externally from UFT, and further that updated script should be saved or loaded back to ALM.

But since UFT doesn’t recognize/follow ALM workflow, even the automated test scripts which are Non Draft status like (For Approval, Approved) are being pulled & modified externally from UFT, and further that updated scripts are being saved or loaded back to ALM(which should not happen, as test script should be in locked stated for Non Draft approval status).

Is there a way to fix the above concern? Can we place control in Script or settings or any where else in the configurations to make UFT work in such a way that it should only be able to access Draft automated test scripts for edit and update and it should not be able to edit/update/ save Non-Draft ALM automated test cases?

Please advise.

Marked as spam
Posted by (Questions: 33, Answers: 21)
Asked on November 2, 2020 9:06 am
Answers (1)
Private answer

Enabling Version Control in ALM would help with this. With that in place, you might be able to create some custom workflow coding that would prevent a script from being checked out for editing, but still be able to run it from UFT.

Marked as spam
Posted by (Questions: 16, Answers: 807)
Answered on April 16, 2021 3:24 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top