Code runner: code language not supported or defined - kotlin

I just finished to setup Kotlin in Vscode, and download Coderunner to run test code such as "Hello world!". However, no matter how I tried, Code runner gave me this error: Code language not supported or defined.
I did almost everything what I can find about this error, however, it kept give me the same result. How can I fix this?
Platform: Ubuntu 20.04

Related

Unable to run my test suite in (Spanish, German or French)

I have a MacBook Pro(macOS Big Sur v 11.4). I am unable to run my test suite in different browser languages like (German, Spanish or French).
I use this command testcafe 'firefox --lang=es' and I have tried both firefox and chrome, I tried --lang=fr and --lang=ger but nothing works.
I tried with double quote testcafe "chrome --lang=fr-Fr" as well.
Everytime I run my test, it execute successfully with no error but always run in English browser language.
And one more thing above code works fine on windows machine.
It seems that on macOS, this method doesn't work out of the box whether or not you use TestCafe.
If you launch chrome with the --lang=fr-FR flag from the console directly (without TestCafe), it will not give the desired result.
Please see the following article and let us know if it helps: https://gist.github.com/kentbrew/e9449acd12c1ef2d78b5b473f615d23b.

"Error" sign in terminal when a run a test

Why does this sign Error: No tests to run. Either the test files contain no tests or the filter function is too restrictive. always come out, if I already do these tests in the TestCafe Studio and did not give an error?
Also, I follow the Pluralsight course, wrote the same code an make the same steps, but still doesn't work.
The TestCafe window pops out but closes automatically after finishing the loading.
Why should I do, or try?
All fixed, was a version misunderstanding... with TestCafe 0.3.0 work immediately. Run
npm install testcafe-blink-diff#0.3.0 to install that version.
Also, I wasn't paying attention, cause the code I need it was on JavaScript, and I was writing down in TypeScript.
For some reason, my google chrome version was a problem too, so I change
Browser: Chrome 75.0.3770 / Windows 10.0.0 to Chrome 76.0.3809 / Windows 10.0.0

TeamCity NUnitTestRunner crashes with Mono 5.4.1

I was wondering why my NUnit tests were suddenly terminating successfully after 30 seconds whereas they usually take at least 20 minutes. Then I looked into the build log and found that after upgrading the mono version on our build agent to v 5.4.1, the test runner crashed with exit code 134.
After doing some research, I found out the following:
- The test runner works when using mono 4.8.1 (which we have installed, too), but the test code won't compile with it
- Ì also tried launching th erunner manually like so: /Library/Frameworks/Mono.framework/Versions/5.4.1/bin/mono -v /Applications/TeamCity/buildAgent/plugins/dotnetPlugin/bin/JetBrains.BuildServer.NUnitLauncher.exe which gave me the following error: [1] 3461 abort /Library/Frameworks/Mono.framework/Versions/5.4.1/bin/mono -v with the 3461changing every time I retry.
- According to this thread, exit code 134 means that the program crashed.
Due to the error output, I am not sure, whether it's the TeamCity test runner that crashes, mono that crashes or TeamCity that makes mono crash.
Any help appreciated :)
I finally figured it out myself. Apparently, Mono 5.4.1 lacks important NUnit2 components that were shipped with Mono 5.2 and older. To make tests work again, I had to add the NUnit.Console NuGet-package (not NUnit.ConsoleRunner as it lacks required extensions) and update the TeamCity build step to use the nunit3-console as described here.
For others that may come across this, I fixed this by changing the NUnit build steps from NUNit 2.6.3 to the NUnit 3.10. I didn't change any of my code / packages, just the TC configuration.

OCaml Error : Fatal error: exception Cmi_format.Error(_)

I'm using OCaml on my Windows device via Cygwin. I installed Opam as well, and also ran the command
opam pin add merlin --dev-repo
because after installing the most recent OCaml for Windows the compiler ocamlc wouldn't work and some Google searching offered this solution.
The error that I got when I first tried to run ocamlc was:
Error: C:\OCaml\lib/pervasives.cmi
is not a compiled interface for this version of OCaml.
It seems to be for an older version of OCaml.
However, now whenever I type "ocaml" in the terminal, rather than getting the interactive editor I get the fatal error message:
Fatal error: exception Cmi_format.Error(_)
Does anybody know what the problem might be? Thank you.
Installed two different versions of OCaml that weren't compatible.

Selenium not working with Firefox 3.x on linux

I am using selenium-server , selenium rc for UI testing in my application . My dev box is Windows with FireFox 3.5 and every thing is running fine and cool. But when i try to run selenium tests on my build server which is a linux box , i get this error
Caution: '/usr/bin/firefox': file is a script file, not a real executable. The browser environment is no longer fully under RC control
basically the selenium-rc is not able to find the firefox executable on linux(actually its a .sh file here), which is present in the case of Windows .
Has anyone faced this error before. Please let me know for any pointers.
Thanks for any help
~Pratik
Thanks!
Pratik
This is occurring because Selenium wants to start the FireFox binary directly, rather than delegate to the normal launch script. Before checking for "firefox" (which is a script on many installations), it checks for "firefox-bin". You can circumvent this problem by creating a link named "firefox-bin" that points directly at your desired version of the firefox binary.
This is described under "Ubuntu fix" (though it actually applies to other Linux'es as well) in the Cucumber Wiki at:
https://github.com/cucumber/cucumber/wiki/Setting-up-Selenium/612fae3f39528be39594d145ec12a4747855e030
Hey, I have Selenium running on Karmic with no issues. I can't quite remember how I did it, but I think it was a case of grabbing a more recent version ot the selenium-rc-serve.jar.
I also remember looking at this post: http://tero.tilus.net/rutinat/2009/08/18/cucumber-running-selenium-on-debian-lenny/
Hope something there points you in the right direction!