Add the ability to specify executor type for Taurus scenario (Use Selenium)

[tbuatois]

Is your feature request related to a problem? Please describe.

I want to loadtest my Single Page Application (SPA) with this tool. Javascript is not enabled on the default taurus executor and so the SPA does not launch.

Describe the feature you'd like

I would like to add the option of choosing an executor for the Taurus scenario like Selenium.

Additional context

I have tested this by modifying the scenario json file and adding a new env variable to the runner. MOZ_HEADLESSto value 1. This enable the headless gecko/chrome driver support without error.

[kamyarz-aws]

Thank you for sharing. We will add this to our backlog for future development.

[ablatov]

Hey, @tbuatois @kamyarz-aws ! So could we please clarify here together what should be implemented to support Selenium executor?

1. UI console/API changes to apply Selenium files packed as zip and as separate TEST_TYPE.
2. load-test.sh script to support handling of Selenium zips.
3. Dockerfile - simple not remove selenium folder from taurus.
   ... other thing I am missing that you consider as important?

Also wonder if it has high or low priority and any plans in the nearest future to be implemented? Thanks!

[kamyarz-aws]

Hey, @tbuatois @kamyarz-aws ! So could we please clarify here together what should be implemented to support Selenium executor?

1. UI console/API changes to apply Selenium files packed as zip and as separate TEST_TYPE.
2. load-test.sh script to support handling of Selenium zips.
3. Dockerfile - simple not remove selenium folder from taurus.
   ... other thing I am missing that you consider as important?

Also wonder if it has high or low priority and any plans in the nearest future to be implemented? Thanks!

@ablatov I am so sorry for the late reply. It seems to be it, you can also look into for inspiration #164
Depending on the version also make sure to adjust dockerfile as well given that we delete selenium dependencies from our image