Katalon won’t start running using the current browser session opened by Katalon

alyaraihanah · January 29, 2026, 2:29am

Hi guys, I’m having an issue where my test suites won’t run. Katalon doesn’t show any error messages, and I’m not sure why. I just moved from Windows to macOS.

Monty_Bagati · January 29, 2026, 3:41am

Common Causes & Solutions

1. Execution Profile Configuration

When migrating projects from Windows to macOS, execution profiles may reference Windows-specific paths or settings that don’t exist on macOS.

Steps to fix:

Open your project and navigate to Project → Settings → Execution
Check your default execution profile (right-click on profile in Tests Explorer and verify it’s set as default)
Verify that any file paths in your execution profile use macOS-compatible paths (forward slashes

/

instead of backslashes

\

)
If using custom global variables with file paths, update them to macOS format

2. Browser Driver Compatibility

macOS may have different browser driver requirements or permissions issues.

Steps to fix:

Go to Project → Settings → Desired Capabilities and verify your browser configuration
For Chrome: Ensure you’re using a compatible ChromeDriver version for your Chrome browser
For Firefox: Verify GeckoDriver is properly configured
Try upgrading/downgrading WebDrivers: Tools → Update WebDrivers (or manually via Katalon’s WebDriver management)

3. Java/JRE Configuration

macOS may have different Java environment setup requirements.

Steps to fix:

Verify your Java version: Katalon Studio → Preferences → Java → Installed JREs
Ensure you have a compatible JRE set (Java 8 or higher recommended)
If needed, set a new default JRE for your test projects: Set a new default JRE

4. Project File Path Issues

Windows and macOS handle file paths differently, which can cause silent failures.

Steps to fix:

Check your test data files and object repositories for hardcoded Windows paths
Update any file references to use relative paths or macOS-compatible absolute paths
Verify that test data files are accessible from macOS (check file permissions)

5. Enable Verbose Logging

Since you’re not seeing error messages, enable detailed logging to diagnose the issue.

Steps to fix:

Go to Project → Settings → Execution → Log executed test steps and enable it
Run your test suite again and check the Console tab for detailed output
Look for any warnings or errors that might indicate what’s failing silently

6. Verify Test Suite Configuration

Open your test suite file and ensure all referenced test cases exist and are accessible
Check that the execution profile selected in the test suite is valid
Try creating a simple test case with a single step (e.g., “Open Browser”) to isolate the issue

Key Considerations

Path Format Differences: Windows uses backslashes (

\

) while macOS uses forward slashes (

/

). Any hardcoded paths in your test cases or global variables need updating.
File Permissions: macOS may require explicit permissions for Katalon to access certain files or directories. Check file permissions if tests reference external resources.
Browser Sandboxing: macOS has stricter security policies for browser automation. Ensure your browser is properly configured for automation.

References

dineshh · January 29, 2026, 5:50am

Path Fixes

Scan Profiles > default > Variables and Test Cases > Data Files for Windows paths like C:\path\to\file.csv. Replace with macOS equivalents: /Users/<username>/path/to/file.csv or relative paths like ./Data Files/file.csv. Use Project > Refresh after edits.

Execution Profile

Go to Project > Settings > Execution. Select default profile; verify Browser is Chrome or Firefox (macOS versions). Run Tools > Update WebDrivers to match installed browsers. Test with Play button on a single WebUI.openBrowser('https://example.com') test case.

Diagnostics

Enable verbose logs: Project > Settings > Test Suite > Log executed test steps > All. Run suite; check Console tab for hidden errors like “File not found” or “Driver mismatch”. Grant Katalon full disk access in System Settings > Privacy & Security > Full Disk Access

kazurayam · January 29, 2026, 8:46am

@alyaraihanah

I looked at the movie you attached in the original post. As far as I see, in the Katalon Studio GUI, you opened a Test Case “Test Cases/Bootcamp/Intensitve Bootcamp/PrePost Test” and ran it. The Test Case passed silently. That’s all you did.

… because you did not start any Test Suite.

You need to open a Test Suite of your interest, keep it focused, and then run it by clicking the button.

grylion54 · January 29, 2026, 7:47pm

Just to note that you do not get any of the reports of your results without starting your Test Case from a Test Suite.

Additionally, you should increase your timeOut amount in your WebUI.scrollToElement() command, from 0 to maybe 10, so like: WebUI.scrollToElement(dynamicAnsObject, 10)

dineshh · February 1, 2026, 11:58am

your query resolved?

depapp · February 2, 2026, 12:50am

this is one example of something that AI cannot do, identifying the core of the problem

most answers that appear to be AI-generated fail to see this as the root cause, even though, upon closer examination, the root of the problem is actually simple, but AI fails to recognize it

kazurayam · February 2, 2026, 4:23am

@alyaraihanah

I thought you did not start any Test Suite, but I am no sure. Am I right or wrong. I am waiting for your reply.

alyaraihanah · February 3, 2026, 6:24am

Hi guys, thankyou for the respond and sorry for the very late update. The issue is I can’t start the test case using my currently open browser by katalon. That’s why I click the arrow button instead of the green play button.

If the issue is related to the file path as mentioned @Monty_Bagati @dineshh , I’ve checked the script and it’s already been switched to the macOS default format.

And this issue happens both when I try to run a test case and a test suite

kazurayam · February 3, 2026, 7:06am

I don’t understand the expression “using my currently open browser”. Is it a new feature that Katalon Studio offers? I don’t know it.

Could you elaborate this a bit more?

alyaraihanah · February 3, 2026, 8:12am

maybe this video would help

depapp · February 3, 2026, 8:31am

hi @alyaraihanah

if you’re looking for the non-enterprise version, you can download directly from here: Release v11.0.0 · katalon-studio/katalon-studio · GitHub

for the macbook with M chip: https://github.com/katalon-studio/katalon-studio/releases/download/v11.0.0/Katalon.Studio.Arm64.dmg
macbook with intel chip: https://github.com/katalon-studio/katalon-studio/releases/download/v11.0.0/Katalon.Studio.dmg

Monty_Bagati · February 3, 2026, 8:38am

Mac OS may have some restrictions or limited access and hence it might not be working

kazurayam · February 3, 2026, 9:33am

@alyaraihanah

I tried to reproduce your issue on my side. I used my macOS 15.7.2. I verified 2 versions of Katalon Studio: 10.4.0 (unpaid) and 11.0.0 (unpaid) on mac.

With v10.4.0, it worked fine.

With v11.0.0, it worked bad. I saw the @alyaraihanah’s issue reproduced.

Therefore I believe that Katalon Studio v11.0.0 has a bug.

→ @duyluong @Shin

I will report what I did in the following post.

kazurayam · February 3, 2026, 9:48am

Katalon provides a sample project healthcare. It contains a Test Case named Main Test Cases/TC1_Verify Successful Login. I used this code as the starting point.

I splitted this code into 2: part1 and part2.

`part1`

import static com.kms.katalon.core.testobject.ObjectRepository.findTestObject
import com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords as WebUI
import internal.GlobalVariable

WebUI.comment('Story: Login to CURA system')
WebUI.comment('Given that the user has the valid login information')
WebUI.openBrowser(GlobalVariable.G_SiteURL)
WebUI.click(findTestObject('Page_CuraHomepage/btn_MakeAppointment'))
WebUI.setText(findTestObject('Page_Login/txt_UserName'), Username)
WebUI.setText(findTestObject('Page_Login/txt_Password'), Password)
WebUI.comment('When he logins to CURA system')
WebUI.click(findTestObject('Page_Login/btn_Login'))

//WebUI.comment('Then he should be able to login successfully')
//landingPage = WebUI.verifyElementPresent(findTestObject('Page_CuraAppointment/div_Appointment'), GlobalVariable.G_Timeout)
//WebUI.closeBrowser()

`part2`

import static com.kms.katalon.core.testobject.ObjectRepository.findTestObject
import com.kms.katalon.core.webui.keyword.WebUiBuiltInKeywords as WebUI
import internal.GlobalVariable

/*
WebUI.comment('Story: Login to CURA system')
WebUI.comment('Given that the user has the valid login information')
WebUI.openBrowser(GlobalVariable.G_SiteURL)
WebUI.click(findTestObject('Page_CuraHomepage/btn_MakeAppointment'))
WebUI.setText(findTestObject('Page_Login/txt_UserName'), Username)
WebUI.setText(findTestObject('Page_Login/txt_Password'), Password)
WebUI.comment('When he logins to CURA system')
WebUI.click(findTestObject('Page_Login/btn_Login'))
*/

WebUI.comment('Then he should be able to login successfully')
landingPage = WebUI.verifyElementPresent(findTestObject('Page_CuraAppointment/div_Appointment'), GlobalVariable.G_Timeout)
WebUI.closeBrowser()

Running the two test cases on v10.4.0

I ran the part1. It worked fine. A window of Chrome browser was opened by the test cases’ WebUI.openBrowser(). The window was left unclosed because the part1 script does NOT call WebUI.closeBrowser().
I opened the part2. I chose the menu of selecting browser type of “Chrome (default) > CURA Healthcare S…”

image990×294 66.9 KB

then the part2 ran successfully.

The browser was closed by the part2 script. This is fine.

Running the two test cases on v11.0.0

I ran the part1. It worked fine. A window of Chrome browser was opened by the test cases’ WebUI.openBrowser(). The window was left unclosed because the part1 script does NOT call WebUI.closeBrowser().
I opened the part2. I chose the menu of selecting browser type of “Chrome (default) > CURA Healthcare S…”

image1932×812 183 KB
Then, the part2 did not start. No processing continued.
in the .log file, I found the following stacktrace emitted:

!ENTRY org.eclipse.e4.ui.workbench 2 0 2026-02-03 21:24:36.299
!MESSAGE c.k.k.c.e.h.AbstractExecutionHandler - Failed to prepare execution request for test case execution.com.katalon.execution.exception.ExecutionException: Cannot determine capability setting for execution.
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler.prepareExecutionRequest(AbstractExecutionHandler.java:1046)
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler$13.run(AbstractExecutionHandler.java:938)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.lang.NullPointerException: Cannot invoke "com.katalon.capability.constant.DriverType.ordinal()" because "driverType" is null
	at com.katalon.capability.factory.CapabilityHandlerFactoryImpl.getCapabilityHandler(CapabilityHandlerFactoryImpl.java:26)
	at com.katalon.capability.manager.impl.CapabilityManagerImpl.getCapability(CapabilityManagerImpl.java:31)
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler.determineCapabilityFromHandler(AbstractExecutionHandler.java:1100)
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler.prepareExecutionRequest(AbstractExecutionHandler.java:1044)
	... 2 common frames omitted

com.katalon.execution.exception.ExecutionException: Cannot determine capability setting for execution.
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler.prepareExecutionRequest(AbstractExecutionHandler.java:1046)
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler$13.run(AbstractExecutionHandler.java:938)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.lang.NullPointerException: Cannot invoke "com.katalon.capability.constant.DriverType.ordinal()" because "driverType" is null
	at com.katalon.capability.factory.CapabilityHandlerFactoryImpl.getCapabilityHandler(CapabilityHandlerFactoryImpl.java:26)
	at com.katalon.capability.manager.impl.CapabilityManagerImpl.getCapability(CapabilityManagerImpl.java:31)
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler.determineCapabilityFromHandler(AbstractExecutionHandler.java:1100)
	at com.kms.katalon.composer.execution.handlers.AbstractExecutionHandler.prepareExecutionRequest(AbstractExecutionHandler.java:1044)
	... 2 common frames omitted

Now we know, v11.0.0 has a bug that causes a java.lang.NullPointerException.

The message

Caused by: java.lang.NullPointerException: Cannot invoke “com.katalon.capability.constant.DriverType.ordinal()” because “driverType” is null

looks trivial to me.

akshay_sartabe · February 3, 2026, 10:35am

The video shows the issues clearly now. This definitely seems bug in Katalon.

But as a workaround could you try Right click on the step and then try ‘Run from here’ option.

I usually do it that way when I want to run scripts from some specific step

alyaraihanah · February 3, 2026, 10:36am

the ‘Run from here‘ option is only work for paid plan. since I use the free version hee

alyaraihanah · February 3, 2026, 10:37am

aaa I see thank @kazurayam for the info

alyaraihanah · February 3, 2026, 10:37am

thanks @depapp I’ll try to download it

depapp · February 3, 2026, 10:42am

i think you don’t need to download the v11 version @alyaraihanah since the issue is on the latest version as @kazurayam explain

if you want to try older version, here’s the link: Release v10.4.0 · katalon-studio/katalon-studio · GitHub

Topic		Replies	Views
Katalon doesn't launch the tests Web Testing katalon-studio	17	3249	July 9, 2019
How to use already opened browser for script execution Web Testing katalon-studio	13	6523	June 25, 2020
Unable to open browser; This version of ChromeDriver only supports Chrome version 77 Web Testing katalon-studio	9	8864	August 12, 2022
Unable to open browser with url (chrome and IE) Web Testing katalon-studio	4	1079	September 24, 2019
com.kms.katalon.core.webui.exception.BrowserNotOpenedException: Browser is not opened Bug Report katalon-studio , bugs-report	17	16244	April 18, 2019

Katalon won’t start running using the current browser session opened by Katalon

Common Causes & Solutions

1. Execution Profile Configuration

2. Browser Driver Compatibility

3. Java/JRE Configuration

4. Project File Path Issues

5. Enable Verbose Logging

6. Verify Test Suite Configuration

Key Considerations

References

Path Fixes

Execution Profile

Diagnostics

part1

part2

Running the two test cases on v10.4.0

Running the two test cases on v11.0.0

Related topics

`part1`

`part2`