Selenium / Scenario
Choose the Binding the Team Can Own
Select a Selenium language from team skills, ecosystem fit, maintenance cost, and migration evidence instead of syntax popularity.
- Difficulty
- Medium
- Format
- Scenario
- Points
- 150
- Estimate
- 13 min
// MISSION BRIEF
Your Mission
Leadership wants one language choice for a long-lived browser suite. Read the team inventory, delivery constraints, and prototype results. Make a contextual recommendation and define what evidence would justify revisiting it.
// FIRST CONTACT
Battle teaser
First artifact
Team and repository inventory
Which binding is the strongest default for the core suite in this specific context?
- AKeep Java for the core suite because ownership, existing libraries, JUnit infrastructure, and near-term delivery all favor incremental work over a rewrite
- BRun half of every test in both languages permanently, regardless of maintenance cost
- CRewrite everything in Python immediately because the prototype uses fewer lines
- DChoose whichever language has the shorter Selenium method names without considering the team
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
selenium-languagepython-vs-javaframework-strategyselenium