update TestRunners for first_script.en.md

[GavinHaydy]

Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.

Description

add document for firstScript #1298

Motivation and Context

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

[netlify]

✅ Deploy Preview for selenium-dev ready!

Name	Link
🔨 Latest commit	4e9ebd5
🔍 Latest deploy log	https://app.netlify.com/sites/selenium-dev/deploys/64196c081e614500082b1eb7
😎 Deploy Preview	https://deploy-preview-1324--selenium-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[diemol]

Thank you, @the-ruffian!

I left some comments.

[diemol]

Actually I am going to let @titusfortner check it because he has a better understanding on how this should look like.

[titusfortner]

I see that we're getting these to match what JS has, but if a user doesn't already know these things, reading this in the documentation is not going to help them.

I think we actually need to create a separate page for this and create a full tutorial.

Probably the best thing to do in this section right now is to describe why to use a test framework, list options, and then link to what we've done in our examples (https://github.com/SeleniumHQ/seleniumhq.github.io/tree/trunk/examples/)

[GavinHaydy]

I see that we're getting these to match what JS has, but if a user doesn't already know these things, reading this in the documentation is not going to help them.

I think we actually need to create a separate page for this and create a full tutorial.

Probably the best thing to do in this section right now is to describe why to use a test framework, list options, and then link to what we've done in our examples (https://github.com/SeleniumHQ/seleniumhq.github.io/tree/trunk/examples/)

That's a good idea. I'll try to do it

[GavinHaydy]

@titusfortner Maybe we can create a “Install Unit test framework” between “Install Driver” and "Fires Script" to write the unit test framework and project configuration.

[titusfortner]

Well, you don't need a test runner to use Selenium if you just want to write a quick script and execute it.

We're trying to support the idea that Selenium is used for more than testing, and that a test framework with a test runner is overkill unless attempting to scale up a testing solution.

"First script" is supposed to be the bare minimum requirements to get Selenium to execute.

But then we point out how testers need to scale up code for a successful testing strategy.

[GavinHaydy]

I finished.
Please check it