You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the Exception thrown by Cucumberish on kotlin/native is not being propagated to swift, causing the program to be terminated by the system, hence error log will be incomplete for the failing test and if a TestPlan sets that a screenshot should be made, that won't happen.
The text was updated successfully, but these errors were encountered:
When Cucumberish is used from K/N a kotlin native bridge is created by passing a lambda to a definition method from Cucumberish (Then, When, Given etc..). That cause the exception thrown inside the lambda by the failed assertion to not be propagated to the test runner where it is trying to catch that CCIException, but instead terminate the programs when that happens.
For now I'm putting aside moving the Cucumber definitions on shared code since also in that case the developer had to declare them twice (on Android and iOS).
To overcome this issue we could take different paths:
Fork and update Cucumberish so that throws an NSError that is propagated correctly to K/N.
Understand and make ForeignException feature work, catch it and return a result type to the call site on swift that throws an NSError.
Right now the Exception thrown by Cucumberish on kotlin/native is not being propagated to swift, causing the program to be terminated by the system, hence error log will be incomplete for the failing test and if a TestPlan sets that a screenshot should be made, that won't happen.
The text was updated successfully, but these errors were encountered: