Why aren't testbeds defined by the workspace?

Question

question

dclaar Suspended asked Jun 10, '09 dclaar Suspended posted Jun 10, '09

Why aren't testbeds defined by the workspace?

If I run a test with itestcli, I can specify which testbed to use, and it will override the testbed stored in the testcase. Why isn't there a way to do that interactively?

One of the most common user errors we run into is that someone opens a testcase, changes a step, and then runs it, trashing the testbed of whomever changed the test last.

The GUI should have almost the same options as the run command:

Use testbed associated with the test case being run
Use testbed associated with workspace
Use specified testbed.

There would also need to be a way to specify a testbed: Set as global testbed (similar to Set as global parameter file) would make a lot of sense.

iTest feature request

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Answer 1 · 2009-06-11T15:27:10Z

PaulD answered Jun 11, '09 PaulD posted Jun 11, '09

You can do this. Just click on the testbed you want in iTest Explorer, right-click and select "Set as Global Testbed" (or something like that -- I'm not in front of it right now). Then when you execute the test, it will prompt you about whether you want that testbed or the one identified in the test case.

1

10 |950

Attachments: Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

dclaar commented · Jun 11, 2009 at 04:57 PM

Cool! I guess I just should have tried to do what I proposed.

Since I converted all of our test cases, and they all have my testbed stored in them, I thank you, and so does my poor testbed!

P.S. We really need some less lame smileys on this board!

0 ·

question