A step-by-step guide to help you integrate AppVeyor with the BrowserStack device cloud for running all your Selenium tests on BrowserStack Automate.
AppVeyor CI is a popular continuous integration and deployment platform based on .NET applications. It makes testing, deployment, and monitoring builds very easy for developers. It is free for open-source projects.
You have access to the BrowserStack account credentials, namely Access Key and Username.
Set up a pipeline in AppVeyor
To create a pipeline in AppVeyor, complete the following steps:
Go to your AppVeyor CI Projects page and click + NEW PROJECT. The Select repository for your new project page opens.
On the Select repository for your new project page, select your SCM, and click + ADD to add your repository.
After your repository is added, click Settings, and then click Build.
Select trigger type for generating build, add the commands, and save the settings.
Click Environment, and add BrowserStack account credentials as environment variables, namely BROWSERSTACK_USERNAME and BROWSERSTACK_ACCESS_KEY.
In your repository, make changes as required and commit to the SCM.
The pipeline runs, and the test result is displayed on your AppVeyor Dashboard page.
Integrate existing test cases
With existing test cases, integrating BrowserStack involves editing your test cases to add BrowserStack capabilities, credentials, and, remote URL.
Though your existing test scripts include capabilities, BrowserStack also provides specific capabilities that help determine how tests are run. The following example code snippet sets session and build name, declares Access Key and Username as environment variables, and creates a remote driver connection.
Using the default APPVEYOR_BUILD_ID and APPVEYOR_BUILD_NUMBER environment variables in the BrowserStack build name helps generate a unique build name for every test run.
Set capabilities using the following code snippet:
username =ENV['BROWSERSTACK_USERNAME']
accessKey =ENV['BROWSERSTACK_ACCESS_KEY']
buildName =ENV['APPVEYOR_BUILD_ID']
buildNumber =ENV['APPVEYOR_BUILD_NUMBER']
caps =Selenium::WebDriver::Remote::Capabilities.new
caps['name']='BStack Build Name: '+ buildName,# test name
caps['build']='BStack Build Number: '+ buildNumber # CI/CD job or build name
driver =Selenium::WebDriver.for(:remote,:url=>"https://"+username+":"+accessKey+"@hub.browserstack.com/wd/hub",:desired_capabilities=> caps)
my$username=$ENV{"BROWSERSTACK_USERNAME"};my$accessKey=$ENV{"BROWSERSTACK_ACCESS_KEY"};my$buildName=$ENV{"APPVEYOR_BUILD_ID"};my$buildNumber=$ENV{"APPVEYOR_BUILD_NUMBER"};my$caps={"build"=>"BStack Build Number:".$buildNumber,"name"=>"BStack Build Number:".$buildName};my$host="$username:$accessKey\@hub.browserstack.com";my$driver= new Selenium::Remote::Driver('remote_server_addr'=>$host,'port'=>'80','extra_capabilities'=>$caps);
Integrate test cases for locally hosted websites
If you are testing websites hosted locally as part of your testing or development environment, you need to configure your AppVeyor pipeline to use the Local testing.
Using the Local testing feature of BrowserStack, remote browsers at the BrowserStack cloud can access websites hosted on your private or internal networks. To learn more about how Local testing works, check out the Local testing guide.
Apart from setting up a Local connection, you must also add the browserstack.local capability in your test scripts.
Using Local binary, the remote browsers in the BrowserStack cloud can access your private or locally-hosted website through the connection established between BrowserStack and the Local binary running on your machine.
To create AppVeyor pipeline that uses BrowserStack Local, complete the following steps:
Under the Build section in the Settings tab, along with the commands that your tests need to run, add the following commands based on your OS.
These commands use the --daemon start and --daemon stop flags to start and stop the Local binary, respectively. To learn about additional flags used in running Local binary, check out the Binary parameter guide.
# For Linux-based systems, add the following commands in the given console to download the binary, run it, and stop its execution after the test has been executed.
$ wget"https://www.browserstack.com/browserstack-local/BrowserStackLocal-linux-x64.zip"
$ unzip BrowserStackLocal-linux-x64.zip
$ ./BrowserStackLocal --key $BROWSERSTACK_ACCESS_KEY --daemon start
$ <your-test-command>
$ ./BrowserStackLocal --key $BROWSERSTACK_ACCESS_KEY --daemon stop
# For macOS-based systems, add the following commands in the given console to download the binary, run it, and stop its execution after the test has been executed.
$ wget"https://www.browserstack.com/browserstack-local/BrowserStackLocal-darwin-x64.zip"
$ unzip BrowserStackLocal-darwin-x64.zip
$ ./BrowserStackLocal --key $BROWSERSTACK_ACCESS_KEY --daemon start
$ <your-test-command>
$ ./BrowserStackLocal --key $BROWSERSTACK_ACCESS_KEY --daemon stop
# For Windows-based systems, add the following commands in the given console to download the binary, run it, and stop its execution after the test has been executed.
$ wget"https://www.browserstack.com/browserstack-local/BrowserStackLocal-win32.zip"
$ powershell.exe Expand-Archive BrowserStackLocal-win32.zip
$ .\BrowserStackLocal-win32\BrowserStackLocal.exe --key %BROWSERSTACK_ACCESS_KEY% --daemon start
$ <your-test-command>
$ .\BrowserStackLocal-win32\BrowserStackLocal.exe --key %BROWSERSTACK_ACCESS_KEY% --daemon stop
Note: To download another Local binary version, check out the releases and downloads section.
If you prefer to manage the Local connection through your test scripts, you can use the language bindings.
Apart from these configurations, you can set other Local options, such as, testing behind a proxy, folder testing, or using multiple local instances. Check out Introduction to Local Testing for more information.
Add browserstack.local capability to test scripts
Add the browserstack.local capability to test scripts using the following code snippets. When you set this capability to true, BrowserStack resolves the request via the Local agent running in your network.