Load another test plan at runtime?

Technical
,
1

I want to create a test step that loads a different test plan at runtime. The TreeView in PathWave should also display the new TestSteps.

  • Is this possible or why isn’t it possible?

I have a lot of use cases and urgently need this logic:

For example, when a new order is scanned (order ≠ previous order), I want to set up the new test plan and execute it directly, etc.

  • What’s the best way to implement this?
  • Do I need a nested structure of multiple sequences?
2

Hi @fauser,

Loading a new test plan as part of the test plan execution itself is not supported. For this kind of use case it is recommended to create a custom operator panel. You can check out an example here: GitHub - opentap/operator-panel: Operator UI Example Project.

You could also have a test plan with sub-sequences for each type of device, maybe using test plan reference and then skip parts of the plan conditionally, depending on the loaded device.

3

Hi @rolf_madsen,

I’m also looking for a solution to this, can you elaborate a bit how the Operator UI could be a solution?

The Test Plan Reference step would solve the issue if the Reference path property could be resolved at runtime ( a previous step to set it). As I know it works only if the path is set an steps loaded before the plan is running, could this be changed?

Thank you!

4

Hi @t_marius,

changing a testplan while running is not possible.

We are using OpenTAP for our testsystems. In our software framework we have 2 OpenTAP sessions running, to solve that problem. So one session is calling tests on another session. This makes it quite flexible.

Br Robin

5

Hi Robin,

We’re currently exploring possible designs for the application and have put together an initial proof of concept with multiple runners sessions and a UI client. It works, but my first impression is that there’s quite a bit of overhead when it comes to data handling. We also need to establish a clear way to enforce consistent topic naming and strict data typing.

6

Hi Marius,

this sounds like same principle we are using.

There is some small overhead bc you need to transfer the data from Session 1 to Session 2. We’ve actually optimized this process quite a bit now. If you’re interested, we’d be happy to discuss it via Teams.