Hi,
when I call a module (module1) from another module (module2) (by TestModuleRunner.Run(module1) method), I would like to see in the report parameters of module1. I have tried to wrap the module1 call with "TestReport.(Begin/End)TestModule()", which creates the module sections in report, which is nice (even nicer would be if they could be nested under the caller module), but parameters of the module1 are still not logged in report like for modules that are called "normally" (from rx test suite).
Is there any way how to tell Ranorex to automatically log these parameters at the start of each test module called dynamically? Without needing to log them manually from inside of the each module.
PS: modules are run conditionally, so I can't use group modules.
Parameters of module called from another module in report
Parameters of module called from another module in report
You do not have the required permissions to view the files attached to this post.
Re: Parameters of module called from another module in report
Hi,
I'm afraid, that there is no out-of-the -box solution for this problem? Using TestModuleRunner.Run is definitely not recommended way of running test modules and therefore, report logger is most probably not optimized for this action. There maybe a solution for this, but I guess it would require some extra coding/editing of report template? Your best hope is to contact directly Ranorex support about this (via support form)?
I'm afraid, that there is no out-of-the -box solution for this problem? Using TestModuleRunner.Run is definitely not recommended way of running test modules and therefore, report logger is most probably not optimized for this action. There maybe a solution for this, but I guess it would require some extra coding/editing of report template? Your best hope is to contact directly Ranorex support about this (via support form)?
Pavel Kudrys
Ranorex explorer at Descartes Systems
Please add these details to your questions:
Ranorex explorer at Descartes Systems
Please add these details to your questions:
- Ranorex Snapshot. Learn how to create one >here<
- Ranorex xPath of problematic element(s)
- Ranorex version
- OS version
- HW configuration
Re: Parameters of module called from another module in report
Sorry to hear that. I thought that if the method is documented in API reference https://www.ranorex.com/Documentation/R ... _Run_1.htm , it should be fully supported. For me it's super useful in lots of cases to avoid copy-paste, save time and to keep test suite clean, since test cases can't be reused.
Maybe it would work by using ActivityStack.BeginActivity event, but it does not seem to be documented at all. I have tried using it, but didn't find way to get current module instance. If I had that, I could easily log the module parameters using reflection. Unfortunately the "TestModuleLeaf.Current" holds the instance of the parent module (caller), not the actual current one that got called dynamically
Maybe it would work by using ActivityStack.BeginActivity event, but it does not seem to be documented at all. I have tried using it, but didn't find way to get current module instance. If I had that, I could easily log the module parameters using reflection. Unfortunately the "TestModuleLeaf.Current" holds the instance of the parent module (caller), not the actual current one that got called dynamically
Re: Parameters of module called from another module in report
While test cases cannot be reused, have you looked into test module groups (linked below)? They are a single container for multiple modules, and in a sense, can be used as a "test case" that can be reused with a single point of maintenance.
https://www.ranorex.com/help/latest/ran ... -elements/ (scroll down to "Module groups" about halfway down).
Re: Parameters of module called from another module in report
As I said earlier, the modules are run conditionally and I can't put conditions inside group module. Next bad thing is group modules cant be nested. It either has to be coded or put inside the testsuite where conditions can be made, but cant be reused. I dont know other way, so the code module is only acceptable solution f9r me.
