The license settings screen in iTest says "... Edit session profiles and test beds in order to target a test case to another set of physical devices" when I select the Runtime edition under "iTest Editions"
However, the users are unable to save the changes to a session profile.
Runtime licenses are for "runtime" i.e. for running tests in regression. They do not allow users ability to save documents.
The documentation that's displayed when you select "Runtime" on the Configure License tab states "Edit session profiles and test beds in order to target a test case to another set of physical devices." Does this mean that one cannot save those edits but instead, the automation should supply these changes via the parameter file or other means?
Thanks, Kumar. This is what I thought. However, the license settings screen in iTest says "... Edit session profiles and test beds in order to target a test case to another set of physical devices" when I select the Runtime edition under "iTest Editions". This is confusing.
To make matters more confusing, if I have an Enterprise or Team license with lots of modules and downgrade to Runtime with all the modules checked, I can then edit the session profile and save it and start a new session without issue. This jibes with the above quoted text.
If I have only a runtime license, I cannot save changes to a session profile or start a new session (the expected behavior, but contrary to the above text).
What am I missing from my understanding that explains this behavior?
I've added a screenshot of the license screen. This is after I started iTest 3.4.4 with Enterprise edition enabled and checked out all modules. I then selected Runtime edition and let iTest restart itself.
I mis-spoke. You are allowed to save Session Profile and Test bed and Parameter documents when you have runtime licenses.
We have a slight discrepancy between Session Profile and Testbed license checker. Session profile license checker checks if you have that module checked out before saving. Testbed license checker does not. We will rectify that appropriately in 4.0.
Thanks, Kumar. So then, if I have a runtime license with ONLY the following contents:
should I be able to save edits to a session profile, since I won't be allowed to check them out?
Currently in iTest 3.4.x, you should be able to do this:
1. session profile document - you will need runtime license and module license to save and start sessions
2. test bed document - you will need runtime license to save but module license is not required. This is a bug. We will fix it. Similarly, to start a session you will need the module license.
