Global list of Environments

Jamie Gagnon, modified 13 Years ago.

Global list of Environments

Padawan Posts: 46 Join Date: 8/27/10 Recent Posts
9 times out of 10 you are testing upgrades to existing infrastructure. So your SUT's are the the same between projects.

What would be good is to have a global list of SUT's where by the user when creating the project and selecting the SUT option. The see the global list where they simply tick the boxes for the specific SUT's covered by the project.

Saves having to key them in over and over again
thumbnail
Torsten Stolpmann, modified 13 Years ago.

RE: Global list of SUT's

Jedi Council Member Posts: 755 Join Date: 2/12/09 Recent Posts
Hi Jamie,

could it be that you are referring to test environments instead of SUT's here?

For environments I would agree that it would make some sense to have templates that could be instantiated upon project creation (e.g. for a list of supported operating systems). But then again a template project itself would be a more powerful solution. What do you think?

Since the test results in a project are directly linked to the environments we like to avoid sharing them as global, cross-project entities.

Regards,

Torsten
Jamie Gagnon, modified 13 Years ago.

RE: Global list of Environments

Padawan Posts: 46 Join Date: 8/27/10 Recent Posts
Yes you are right Torsten I have renamed the header accordingly.

A template project would be very powerful as a user can set the template up the way they intend to use it on projects and copy it each time they create a new project.