To enable "target platform" support for driver types, I could definitely benefit from the availability of the "personality" values provided by SeleniumGrid. However, launching the local grid servers for this purpose makes no sense. To expand the utility of the "personalities" collection. the servers attached to local grid hub and node objects shouldn't be launched until we actually need a driver session.
It may be beneficial to revise the DriverPlugin interface to revise the output of getPersonalities() to return a map that associates personalities with plug-ins rather than capabilties.
To enable "target platform" support for driver types, I could definitely benefit from the availability of the "personality" values provided by SeleniumGrid. However, launching the local grid servers for this purpose makes no sense. To expand the utility of the "personalities" collection. the servers attached to local grid hub and node objects shouldn't be launched until we actually need a driver session.
It may be beneficial to revise the DriverPlugin interface to revise the output of
getPersonalities()
to return a map that associates personalities with plug-ins rather than capabilties.