Details
-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
2018 Week 48-50
-
2
-
NEW
-
NEW
Description
Until now, QE selenium tests were relying on several heuristics to distinguish which workbench they are running with (kie-wb/kie-drools-wb). This was necessary to handle product differences between DM/PAM in tests. E.g. we were looking at
- page title (unreliable as it changes based on the page you're on)
- logos (unreliable, because there are some screens that don't show logo)
- context-root (unreliable, because e.g. swarm distro uses empty context root).
Now that the workbenches have been consolidated into one and there is the new concept of the profile, we're looking for a new (and reliable) way to detect which profile is currently enabled (without having to navigate to Profile settings and looking there, which wouldn't work with the new "FORCE_" functionality anyway).
I was thinking of simply putting some (hidden) element somewhere in the DOM, which would contain the info about profile being enabled like
<div id="enabledProfile" style="display: none;">FULL</div>
Could you help us decide what's the best place in the code where something like this could be added? Maybe it could be added to the MegaMenu which is available mostly everywhere? Or maybe you can think of different mechanism we could use to identify the currently active profile (from selenium tests that only have access to the browser's dom and page title, but not much more)?