Couldn't identify test method in call stack. This is needed to dynamically name the Golden Master files. Please call `startTest("name")`, giving an explicit name, or instantiate RecheckImpl with RecheckOptions, and provide a different FileNamerStrategy.
Sha-123 opened this issue · 6 comments
Hi, actually i am getting this error when run code using normal java code.
Please help with this one.
The reason that i am not using testng or junit because our company is developing a automation product, but the product used only java code to automate. but i am having bit confusion over the filenamerStratagy. please help with the naming stratagy.
Hey @Sha-123,
FileNamerStrategy is actually deprecated, will update the error message accordingly.
However, if you are not using a test framework we are aware of, you can configure the test name via Recheck#startTest( String ). Or, you can use the new NamingStrategy class. Please have a look at the following docs and let us know if this solves your issue:
Hi @beatngu13 ,
Thanks. Now I can resolve this issue in eclipse by implementing namingStratagy but as i mentioned earlier if i run this code in the automation product we are developing, getting new error as
de.retest.recheck.RecheckAdapter: Provider de.retest.web.RecheckSeleniumAdapter could not be instantiated.
I have no idea about this adapter. please help me with this error.
The adapter is only used internally, however, it is the central part to communicate with recheck as it is converting the WebDriver into the domain specific data structure so that it can be used to do the difference testing. This part is referred in the documentation as "extension" and is looked up via the SPI API which apparently is not able to instantiate the RecheckSeleniumAdapter (probably due to an exception occuring).
However, with only the message of the stack trace, we are not able to identify this exception. Are you able to provide the stacktrace (first couple of lines) and the exception preventing the instatiation? This is likely a InvocationTargetException due to reflection access of the ServiceLoader.
It would be also helpful to know which Java version you are using and if you use the Java 9 module system which might restrict the reflective access.
I assume this is fixed now, closing due to inactivity. If you or any other still have problems, please comment and reopen this issue.