Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Thursday, May 28, 2020

Chromedriver version error


The one error that I have ran into a few times by now is the version mismatch error between the Chrome application and the chromedriver on my machine (Mac OS)

SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 83

For most of my project I had an alias for chromedriver getting added in the lib folder (It would show up after successful execution of a test case but I need to figure out why it was showing up there). I would simply download the latest chromedriver version and drop it in the the original location of the driver-alias in the project. 

However just started a new project after not working on automation for past one year. In this new project the chromedriver alias is not getting added to project (again need to find out why not, what is diff between the two projects). While working through other issues today I landed back at this error (obviously I was demoing at the time, meh) and without the alias had to go googling about the error. 

So to fix the issue there are two possible solution
1. Update the chromedriver executable to the correct version manually OR
2. Use chromedriver-manager package to handle all the version management

Solution 1:

  1. Download the correct driver version from https://chromedriver.chromium.org/downloads
  2. Unzip the file
  3. Manually copy the executable to /usr/local/bin (overwrite the previous version in folder)
Solution 2:
I have not tested this solution yet but the idea makes sense. Will Need to understand how it works. https://stackoverflow.com/questions/60296873/sessionnotcreatedexception-message-session-not-created-this-version-of-chrome


As always solution 1 has resolved the error, so I'll move on with the other issues on project. 


To Do:
  1. Why is chromedriver alias created in project 1
  2. Why is chromedriver alias NOT created in project 2
  3. Find out how solution 2 works and to set it up



Friday, July 1, 2011

CLR version error on starting Nunit

I am totally new to Nunit and creating test cases in VS for it, so I google for tutorial, follow the steps word by word try to pull the project in NUnit and am received by a lovely window


Makes me feel either I am too dumb or Nunit needs to test their own product (least they could do is have some user friendly message and direct to proper documentation)

But things are not meant to be simple in ITville so I call upon my dear friend Google to help me out again and found a solution for how to fix it here

Just copying over the solution for ease of reference:
Open the nunit-x86.exe.config file (My file is at C:\Program Files (x86)\NUnit 2.5.10\bin\net-2.0)
Under <configuration> add:
<startup> 
     <supportedRuntime version="v4.0.30319" /> 
</startup>

and under <runtime> add:
<loadFromRemoteSources enabled="true" />

NOTE: It is always a good idea to leave the original setup files untouched (just in case you screw up something). Normally I rename the original file by adding a .ORIG extension, make its copy and then do any changes that I want.

If you still happen to get the same error every time you open NUnit, then delete all the shortcuts for NUnit and create a new one from the .exe in the bin folder again.

Credits: http://stackoverflow.com/questions/930438/nunit-isnt-running-visual-studio-2010-code