SeleniumHQ / SeleniumHQ/selenium

[🚀 Feature]: [dotnet] Revisit unit tests infrastructure

Open
#15,536 4 comments 1 reaction 0 assignees View on GitHub
C-dotnet I-enhancement
Dominant language
Java
Stars
34.5k
Forks
8.7k
Avg merge
2d 1h
Merged PRs (30d)
92

Description

### Feature and motivation

Current situation is:

![Image](https://github.com/user-attachments/assets/97f1b7d2-180c-4a6e-9177-9731f39eb822)

### Usage example

Concerns:
- It could be one test project because Chrome/Edge/Firefox drivers live in one project supported by Selenium (like built-in classes).
- Default namespace in test project is `OpenQA.Selenium` when usually it should be `OpenQA.Selenium.Tests`. I don't understand why it is unusual.
- Avoid any `static` context (`EnvironmentManager` class) - it will allow to look at parallelization. My computer has 6/12 cores, I want to utilize all of them when running Selenium unit tests.
- Provide a possibility to override driver options, like required in https://github.com/SeleniumHQ/selenium/pull/15850

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.