SLF4J: The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]


hello katalon community,
i am a new user here and a beginner with automated tests in java.
after installing katalon, record test case in chrome browser, i always received error message and test running is stopped.

Note: i am using OS: windows 10, my test case is very basically.

this is my console result:

SLF4J: The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]
SLF4J: See for further details.
2018-12-08 12:17:48.110 e[34mINFO e[0;39m e[36mc.k.katalon.core.main.TestCaseExecutor -e[0;39m e[39m--------------------e[0;39m
2018-12-08 12:17:48.110 e[34mINFO e[0;39m e[36mc.k.katalon.core.main.TestCaseExecutor -e[0;39m e[39mSTART Test Cases/agurae[0;39m
2018-12-08 12:17:48.837 e[39mDEBUGe[0;39m e[36mtestcase.agura -e[0;39m e[39m1: openBrowser("")e[0;39m
2018-12-08 12:17:49.296 e[34mINFO e[0;39m e[36mc.k.k.core.webui.driver.DriverFactory -e[0;39m e[39mStarting ‘Chrome’ drivere[0;39m
2018-12-08 12:17:49.342 e[34mINFO e[0;39m e[36mc.k.k.core.webui.driver.DriverFactory -e[0;39m e[39mAction delay is set to 0 secondse[0;39m
Starting ChromeDriver 2.43.600210 (68dcf5eebde37173d4027fa8635e332711d2874a) on port 14369
Only local connections are allowed.
Dec 08, 2018 12:17:52 PM org.openqa.selenium.remote.ProtocolHandshake createSession<

what can i do with the 2 first error message above? there is any solution?


Does your test execution continue?

I belieive this is only a warning. I have also seen it in my logs but haven’t noticed it did anything.


Yes, the error is just a warning. We will look for a way to resolve it in future releases. For now, it is safe to ignore it.


Hi! I think it’s just a warning. Doesn’t cause any error on my side. I’m also getting that on my console at the beginning when I run my scripts.


TNX for your comments.
After that error, my test execution start and crushed, every time in different location of the test.
so you all said that my crushed in not as a result of this error?


No, it should not. Don’t hesitate to start a new topic with the execution logs- we’re happy to help.


Thank you very much, I’ll do it


Use old version. katalon 5.5 version is not gave this error. I think katalon new update is not work correctly. If you have katalon old version you can test your project properly.



I’m pretty new to automation and Katalon Studio tool, please bear with me.

I’ve been receiving this error when I’m attempted to create BDD test via this video tutorial:

And I receive this error:

SLF4J: The requested version 1.7.16 by your slf4j binding is not compatible with [1.6]
SLF4J: See for further details.
2019-02-19 17:15:50.208 INFO c.k.k.core.main.WSVerificationExecutor - --------------------
2019-02-19 17:15:50.210 INFO c.k.k.core.main.WSVerificationExecutor - START Verification
2019-02-19 17:15:51.007 INFO c.k.k.c.c.k.CucumberBuiltinKeywords - Starting run keyword runFeatureFile: ‘Include/features/1. Login (TOT-4348)/Login.feature’ and extract report to folder: ‘/var/folders/z_/2tzgf8t12xj72n2kwcr591x00000gr/T/Katalon/Include/features/1. Login (TOT-4348)/Login.feature/20190219_171544/cucumber_report/1550596550998’…

0 Scenarios
0 Steps

2019-02-19 17:15:52.281 INFO c.k.k.core.main.WSVerificationExecutor - END Verification

Anyone have any ideas why this is? Any help would be greatly appreciated.


Hi, as above, it is just a warning, I also have the same showing in console but after fixing the errors shown after it there were no more issues. Ignore it and focus on the errors below that first and see what happens. If what you have posted is your entire console output I don’t actually see the issue?


Well, reading above responses, even if that error is warning, could we get ticket to resolve that ?
For someone new to Katalon, the error might confuse them.
Also, if we have a workaround of same, we can share it in broader forum as well


Is issue mentioned above fixed in latest release i.e. Katalon 6.2


I ran my tests yesterday a few times with no issue and then I upgraded ( 6.2.1) .and now I am getting the exact error as stated above. Is there a fix for this issue??