About OpenTAP GUI

1

Hello,

I am quite new in using OpenTAP and I noiced that everytime we are making any changes in our testplans we need to restart (close and open the GUI), any way to avoid that?
I am using the GUI on windows.

Best Regards,

Arash

2

Hi @arashshb and welcome to the forum!

I have not noticed that when changing test plans, but it definitely is the case if you make code changes. Are you making any code changes?

3

Hello @rolf_madsen ,

Thank you for your response, yes, I was wondering if there is a way to change your code and you reload in the editor instead of closing and opening the editor GUI. I checked with some other colleagues and it seems in the previous versions there was a chance to do that, do you have any idea if this point is fixable?

best Regards,

Arash

4

This is something we would like to support, but unfortunately it is very hard in practice.

If you are programming C#, Visual Studio has an edit-and-continue feature which works for small modifications.

If you are programming Python, its a topic we still need to figure out how to do. Simply reloading the .py file does not help at the moment.

5

Hello @rolf_madsen ,

can you please explain why it is not techniacally possible? I mean I want to know if I can contribute there?

BR,

Arash

6

Hi @arashshb,

I never said that it’s not technically possible. It’s just that we don’t know how yet.

Also, I don’t have a clear picture of what you are trying to do,. If you could clarify that I might be able to say more.

7

Hi @rolf_madsen ,

I have a testcase to measure the output power of CMW100 and when I make a change in my testcase I need to close and re open the editor which is bothering. I want to know if we can manage to find a way to avoid this. I know it is due to the python but I want to get to know exactly what is the issue that we need to close and open the opentap editor. Any guidance is more than appreciated. I do not know if there is a chance to have a talk and share my screen to show you the issue that I mean.

best Regards,

Arash

8

Hi @arashshb,

Maybe a better way could be to create a test plan and run it via the command line interface? That is a bit faster than opening the Editor application. So if you just want to optimize that inner loop while debugging, that could be the fastest approach.

Save the test plan from Editor.exe and run from the application folder:

tap run pathToTestPlan.TapPlan