Wrong driver version

[ludys1]

Hi Yevgeniy!

We are using your framework in a project and the day before yesterday our tests started to failing. We are bulding our tests through github actions the build is succesfull but all tests are failing because of the wrong chrome version as far as I understand the error message below:

A total of 1 test files matched the specified pattern.
Starting ChromeDriver 92.0.4515.43 (8c61b7e2989f2990d42f859cac71319137787cce-refs/branch-heads/4515@{#306}) on port 36785
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
X BE_UserWantsToCreateANewBusinessUnit [871ms]
Error Message:
System.InvalidOperationException : session not created: This version of ChromeDriver only supports Chrome version 92
Current browser version is 91.0.4472.164 with binary path /usr/bin/google-chrome (SessionNotCreated)

Locally the tests are working as I have the latest chrome version but when running on the server with such configuration its not working:

name: Tests Run
on: 
  workflow_dispatch:
  repository_dispatch:
    types: [be_deployed, fe_deployed]
jobs:
  build:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        dotnet-version: ['3.1.x']

    steps:
    - name: 'Checkout iFLOW.testing'
      uses: actions/checkout@v2
    
    - name: Setup .NET Core SDK ${{ matrix.dotnet-version }}
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: ${{ matrix.dotnet-version }}
    - name: Install dependencies
      run: dotnet restore
    - name: Build
      run: dotnet build --no-restore
    - name: Test
      run: dotnet test --logger:"nunit;LogFilePath=Reports/test-result.xml" --no-build --no-restore
      continue-on-error: true
    - name: Get Xray Cloud API token
      env:
        CLIENT_ID: ${{ secrets.CLIENT_ID }}
        CLIENT_SECRET: ${{ secrets.CLIENT_SECRET }}
      id: xray-token
      run: |
        echo ::set-output name=XRAY_TOKEN::$(curl -H "Content-Type: application/json" -X POST --data "{ \"client_id\": \"$CLIENT_ID\",\"client_secret\": \"$CLIENT_SECRET\" }" https://xray.cloud.xpand-it.com/api/v2/authenticate| tr -d '"')
    - name: Submit results to Xray
      run: 'curl -H "Content-Type: text/xml" -H "Authorization: Bearer ${{ steps.xray-token.outputs.XRAY_TOKEN }}" --data @/home/runner/work/IFLOW.testing/IFLOW.testing/Reports/test-result.xml  "https://xray.cloud.xpand-it.com/api/v2/import/execution/nunit?projectKey=IB"'

there is no chrome configuration so I guess the version needs to come somewhere from atata config, but I dont have any specific version choosed anywhere:

config:

AtataContext.GlobalConfiguration
    .UseChrome()
    .WithArguments("start-maximized")
    .UseCulture("en-US")
    .UseAllNUnitFeatures()
    .ApplyJsonConfig<AtataConfig>();

atata.json:

{
  "drivers": [
    {
      "type": "chrome",
      "alias": "chrome",
      "options": {
        "arguments": [ "start-maximized" ]
      }
    },
    {
      "type": "chrome",
      "alias": "chrome-headless",
      "options": {
        "arguments": [ "headless", "window-size=1920,1080" ]
      }
    }
  ],
  "baseUrl": "",
  "culture": "en-US",
  "useAllNUnitFeatures": true
}

Can you help me to resolve this problem?
Greetings from Poland,
Filip.

[YevgeniyShunevych]

Hi FIlip,

Currently, for Chrome driver the auto setup functionality tries to detect the installed browser version only on Windows. For Linux and macOS it just installs the latest driver version available. Let me try to find and implement the similar browser version detection for Linux shortly. Will keep you posted.

Until then, if you need to fix your pipeline now, you can do one of the following:

1. Update your pipeline yaml to run on Windows instead of Linux.
2. Instead of AtataContext.GlobalConfiguration.AutoSetUpDriverToUse(); do DriverSetup.ConfigureChrome().ByBrowserVersion("91").SetUp();.

[ludys1]

Thanks man I used the second solution and it worked! My PO will be very happy so thanks again :P

[YevgeniyShunevych]

Filip, I've just released Atata.WebDriverSetup v1.2.0 with added Chrome version detection for Linux and macOS. You can update the reference in your project. Please, let me know if it will not work for you.

[YevgeniyShunevych]

Hi Filip,

OK, it got ChromeDriver v94, but Chrome browser was v93. Could you please share the code that sets up driver?

[ludys1]

public sealed class SpecFlowHooks
{
private static ReportPOCO reportPOCO;

    [BeforeTestRun]
    public static void StetUpTestRun()
    {

        AtataContext.GlobalConfiguration
            .UseChrome()
            .WithArguments("start-maximized")
            .UseCulture("en-US")
            .UseAllNUnitFeatures()
            .ApplyJsonConfig<AtataConfig>();

        AtataContext.GlobalConfiguration.AutoSetUpDriverToUse();

        reportPOCO = new ReportPOCO();
        Reporter.SetupExtentReports();

    }

the pipeline runs on ubuntu

[YevgeniyShunevych]

Thanks, looks fine. Could you also try to download from CI system and share content of \drivers\chrome\versioncache.xml file. It should be located in working build folder of tests project?

[ludys1]

Our app is hosted on azure and I couldn't found any folder with chrome :( I have changed the setup to DriverSetup.ConfigureChrome().ByBrowserVersion("94").SetUp(); and this solution is working but we will have to change the verison after every new release so this is more like a temporary solution

[YevgeniyShunevych]

drivers folder should be located in the build folder of tests project, where all other .dll files are built. This directory should definitely be there, as it used to store driver executables. You can, for example, add "publish artifacts" step to your pipeline to publish build folder. And that check files in published artifact zip file.

That \drivers\chrome\versioncache.xml file is important to figure out whether Atata.WebDriverSetup was able to get installed Chrome version. I guess that it was not able to read the installed version and in such case it uses the latest version.

For example, below is the content of versioncache.xml file when installed version was successfully read:

<versions>
  <version browser="94.0.4606.61" driver="94.0.4606.61" timestamp="2021-10-04 13:23:43Z"/>
</versions>

And this is the example of a case when the latest version was used:

<versions>
  <version browser="latest" driver="94.0.4606.61" timestamp="2021-10-04 13:23:40Z"/>
</versions>

By the way, Atata.WebDriverSetup detects installed version of Chrome on Linux using google-chrome --product-version command. If you are able, try to execute this command on build Linux machine. Otherwise, you can even add a simple pipeline step that execute this command, and after the build run, check what this command returns.