Any Suggestions on how to Moving Resources (tests, scripts) From Project to Project in QC?
Question ID: 108779

Currently we have two Business Units that have their own instances of QC ALM up, we have a future project plan to move some teams from one major legacy project instance, to individual team projects int eh other BU instance.

So my question to you folks is this: What are the best practices in moving test and automation script resources from one instance to another?

Also, as we take our teams to their individual projects, one thing that will be important is resource sharing. Is there an appropriate way to share resources/tests/scripts across multiple projects?

One problem we will need to solve with everyone maintaining their own project is template sharing of automated scripts, etc.
Any help is appreciated.


Marked as spam
Posted by (Questions: 193, Answers: 14)
Asked on December 18, 2018 9:12 pm
Answers (1)
Private answer

This request (sharing entities between projects and maintaining a ''pool'' or ''template'' of resources) is WHY the ''ALM-level'' license exists for Quality Center.

With the ALM license (instead of ''enterprise''), you can setup a ''baseline'' (with content like tests and requiements) and ''publish'' various entities across projects. Some companies maintain a ''master'' library of these entities and ''publish'' parts out to various smaller projects.

Another feature of ALM is the concept of having a ''template'' project containing customizations (custom workflow and fields) and initial structure (folders), then this template can be used to create projects with the same structure and later push additional customizations down.

If you don't have the ALM licence, you are left with the old multiple IE instances showing different QC projects (at same version like both running QC12.55), then doing copy to clipboard, then paste into target project. Be careful not to grab too large of a ''chunk'' (of the test tree for example) or you may hit a maximum items copy limit or memory limit.

As for copying cusotmizations, you could have a ''base'' project that contains all of the basic starting point for your projects (like custom fields and workflow pre-defined and any starting folder structures), then when you need a new project, create one based on this one. After that, make sure to do any new customization additions to the ''base'' AND all other projects at the same time.
Be careful with adding custom fields -- each one gets the next consecutive integer (e.g. BG_USER_02, BG_USER_03, etc.). If the admin(s) add(s) random additional custom fields willy-nilly to the projects, different numbers get assigned to the SAME named field in different projects. This is not a big deal... UNLESS you want to combine data from different projects in a REPORT ... OR Copy it from one project to the other.

Yet another feature of ALM license is ''cross-project reporting'', where you can grab data from more than one project (assuming the data structure is the same, or almost the same).

Marked as spam
Posted by (Questions: 4, Answers: 509)
Answered on December 18, 2018 9:32 pm
We do not have ALM-level license, but have 'enterprise'' so cannot do any cross-project stuff or templates. I guess for now we will create ''base'' project from original and copy/paste various tests and other entities over and live with potential loss of links/coverage.
( at December 18, 2018 9:34 pm)

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

Scroll to Top