selenium-side-runner to show which steps are done similar as in IDE

[etvoorde]

🚀 Feature Proposal

Show in selenium-side-runner what steps are done similar as in IDE

Motivation

I am dealing with tests that works fine in IDE, but throw errors in the side-runner. Errors like ElementNotInteractableError, ElementClickInterceptedError. As I don't know at which steps that happens, it is difficult to analyse.

[Martin-Hogge]

Did you find something to see the steps with the command line runner ?
Or did you find the cause of you ElementNotInteractableError ?

[doanva84]

Hello,
I recommend below tricks.

1. Under 'Export' dialog, Check 2 check-boxes 'Include origin tracing code comments' & 'Include step description as a separate comment'
2. Wrap comments with logging code. For example:
   • JavaScript: console.log('')
   • Python: print('')

P/S: In fact, you could use replace-All feature of Notepad++ or modern editors to perform step '2.' quickly.

[jploski]

Too bad there is no way to log the individual commands with selenium-side-runner as that would be very useful for determining which step of the test failed (the thrown exception often is not).

Anyhow, as a quick workaround, you can hack the "selianize" module, which is what emits the Javascript code which drives the actual test. In my case, by editing /usr/lib/node_modules/selenium-side-runner/node_modules/selianize/dist/selianize.cjs.js and patching the function emit$4(command, options = config, snapshot) as follows:

-        res(result);
+        res('console.log(\'' + command.command + ' ' + command.target.replaceAll('\'', '\\\'') + '\');' + result);

As a side note, if you want to hack the generated test code, you can do so by running selenium-side-runner with --debug (to see where it is written to) copying that directory away (your test code is in commons.js inside of it; note selenium-side-runner will automatically delete the directory after the test) and then executing the code from the copied directory directly (rather than regenerating it) by setting the environment variable NODE_ENV=development and using the selenium-side-runner option --run /path/to/your/directory/with/commons.js (the option --run is undocumented and only available with NODE_ENV=development).

[toddtarsi]

@jploski - On v4 thats '-d', and you can also see all the options by just calling selenium-side-runner --help.

[jploski]

@jploski - On v4 thats '-d', and you can also see all the options by just calling selenium-side-runner --help.

Thanks - still running 3.17.0 here (where the option was implemented, but not documented in --help output.