https://github.com/bvisagie/extensible-dotnet-selenium-automation-framework
.NET 5 based boilerplate automation framework with the purpose of being extensible and getting you up and running fast. It is also ready for multithreaded / concurrent test execution. Built with the eventual release of Selenium 4.0.0 in mind. (Currently Alpha 7)
https://github.com/bvisagie/extensible-dotnet-selenium-automation-framework
csharp selenium selenium-webdriver selenium4
Last synced: about 2 months ago
JSON representation
.NET 5 based boilerplate automation framework with the purpose of being extensible and getting you up and running fast. It is also ready for multithreaded / concurrent test execution. Built with the eventual release of Selenium 4.0.0 in mind. (Currently Alpha 7)
- Host: GitHub
- URL: https://github.com/bvisagie/extensible-dotnet-selenium-automation-framework
- Owner: BVisagie
- License: mit
- Created: 2020-11-19T18:37:13.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2021-07-23T06:32:24.000Z (almost 5 years ago)
- Last Synced: 2025-01-16T09:54:32.009Z (over 1 year ago)
- Topics: csharp, selenium, selenium-webdriver, selenium4
- Language: C#
- Homepage:
- Size: 32.2 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Extensible Test Automation Framework
This is a starter or boilerplate test automation framework with the capability of automating both UI and non UI test cases; the base of the framework also aims to be maintainable and extensible.
## Usage
### Installation
To install Extensible Automation Framework (EAF), simply clone and rebuild the project. Should the NUnit tests not be automatically picked up, you can configure local.runsettings file from Visual Studio: `Test--> Configure Run Settings --> Select Solution Wide runsettings File`
# Build and Test
NUnit Framework manages tests, you may use Test Explorer to browse available example tests and run from there.
If you run in Release mode, the Chrome Browser will might start headlessly, i.e. nothing will appear; to see what is happening, run tests in debug mode.