Are you using ALM Lab Management?

I don't know if you are referring to the Management (Releases) section. In that case, we don't use it.

We only use the test sets within the Test Lab section, where we have all the template test sets and others that we created separately.

Hi Ramon

No I'm referring to the Lab Management module in ALM for server-side test execution and execution scheduling, and things like build verification suites integrated to CD/CI systems as described here

https://admhelp.microfocus.com/alm/en/24.1/online_help/Content/UG/t_create_build_verification_suite.htm

Maybe you can describe the process you are doing when you have a new release to test, and where the test set copying actually comes into play.

You mention that you are testing multiple releases yet you don't use the Management module ( Releases, Cycles ) to organize your tests in ALM, so I'm a bit puzzled on why that is the case.

One additional thought.

If your question is simply about how to automate the copy of test sets, then you may want to look at the REST API documentation for ALM

Hi machinedata.

Unfortunately we don't have the Lab Management module.

The test sets are created manually and we simply duplicate them manually as well.

We don't have anything registered in the releases section of ALM.

Is this the link for the documentation of REST API for ALM?

ALM REST API Reference (Core) Overview (microfocus.com)

Yes that's the correct link.

By the way you should have your team use the ALM releases/cycles capabilities and pin your test sets to those cycles when you create or instantiate them.  Also to have a look at libraries.  They can reach out to us if they need help with understanding how to use these capabilities.

With ALM -- as with any system -- it's equally important to report and track the planned and completed activity in the system. The releases and cycles capabilities are vital for organizing and distinguishing which tests, runs, defect belong to which release.  If your teams aren't using these capabilities, how are they associating or linking these things for reporting purposes?

An in some cases you can avoid the issue of duplicating test sets simply by pinning the existing ones to the release/cycle that it belongs to.

In principle, what interests us is to be able to copy the group of test sets called TEMPLATES and inside all the necessary test sets, and then "automatically" change the name associated with the corresponding release. This is how the client himself wants to do it from this point.

By the way, looking at the REST API documentation indicated above, it seems to me that it is very complicated to do what we need because we barely have knowledge of APIs.

Could this be done with VBScript code using the OTA service? Perhaps it is the best to carry out this process.

Yes you should be able to use the OTA API as well.

Is there documentation about OTA in ALM?