Saucery handles all the plumbing required to integrate with SauceLabs, making writing tests a breeze. so you only need to tell Saucery what you want. Saucery takes care of the how.
Saucery comes in multiple flavors supporting popular test frameworks.
The templates below include example tests.
Package | Badges |
---|---|
Saucery | |
Saucery.XUnit | |
Saucery.TUnit | |
Saucery.XUnit.v3 |
Saucery has been developed as an open-source project for over 10 years. If you find it valuable for your projects and team work, please consider supporting it and becoming a
We test Saucery itself on SauceLabs!
These steps apply to all flavors:
- You'll need a SauceLabs account. You can get a free trial account here.
- If you want to run your tests locally you need to set 2 environment variables, SAUCE_USER_NAME and SAUCE_API_KEY
- To run your test suite from your GitHub Actions pipeline you need to set two secrets SAUCE_USER_NAME and SAUCE_API_KEY. Instructions on how to set Github Secrets are here.
cd Templates
dotnet new install .\NUnit
dotnet new saucery-nunit -n "MyTestProject"
cd Templates
dotnet new install .\XUnit
dotnet new saucery-xunit -n "MyTestProject"
cd Templates
dotnet new install .\TUnit
dotnet new saucery-tunit -n "MyTestProject"
cd Templates
dotnet new install .\XUnit3
dotnet new saucery-xunit3 -n "MyTestProject"
Platform range expansion is a feature unique to Saucery. Say you wanted to test on a range of browser versions but you didn't want to specify each individually. That's fine. Saucery supports specifying ranges.
new DesktopPlatform(SauceryConstants.PLATFORM_WINDOWS_11, SauceryConstants.BROWSER_CHROME, "100->119")
This will test on Windows 11 Chrome all available versions from 100 to 119 inclusive.
Yes, Saucery supports Real Devices!
Author: Andrew Gray
Twitter: @agrayz