In Cucumber, if there is an exception in the beforeScenario handler, the afterScenario is not called. Catch the exception in the beforeScenario and free the device in such a case.

Longer version: For each new test that starts running, ATD marks a device "busy" before creating a new driver instance from the beforeScenario. When running a suite of tests, if there is a problem in the driver initialisation resulting in an exception for each test, eventually all devices end up getting marked as "BUSY" in beforeScenario. Once all the devices are "busy", for subsequent tests, there are no available devices, and the thread ends up in suspended state till some device becomes "free". The solution is to catch the exception when creating the driver, and in this case, free the device before re-throwing the exception.

Author: anandbagmar

src/main/java/com/cucumber/listener/CucumberScenarioListener.java

@@ -66,7 +66,11 @@ private AppiumDevice allocateDeviceAndStartDriver(String testMethodName) {
             }
             return updateAvailableDeviceInformation(availableDevice);
         } catch (Exception e) {
+            LOGGER.error(String.format("Error creating / allocating a driver for test: '%s'%n%s",
+                                       testMethodName, e));
             e.printStackTrace();
+            LOGGER.info("Releasing the device that was allocated");
+            deviceAllocationManager.freeDevice();
             throw new RuntimeException(e);
         }
     }