Defect: Ready API Pro 1.5 throws BadSqlGrammarException error when running test cases with listeners
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Defect: Ready API Pro 1.5 throws BadSqlGrammarException error when running test cases with listeners
Ready API Pro 1.5.0 throws BadSqlGrammarException error when it finishes running test cases that contain listeners. This causes the steps in the test case window to remain greyed out and to be unresponsive to mouse clicks. It also breaks running in a loop--you only get through the first loop then the exception makes it stop. You can still manually play the test case again, but you'll get the error at the end every time.
These are test cases that work perfectly fine in Ready API 1.3.1 and earlier, even after trying to run them in 1.5.0.
Work Around: Go back to Ready API 1.3.1.
Error:
EST 2015:ERROR:Error notifying listener after run
org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [select * from test_step_run_history where execution_id = ?]; nested exception is org.h2.jdbc.JdbcSQLException: Column "icon_path" not found [42122-176]
See the attached file for the full stack trace.
Solved! Go to Solution.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Thanks for reporting the issue. I've submitted it to our R&D team. While we are waiting the news from them, could you please check if the issue persists in the latest nightly build? https://support.smartbear.com/downloads/readyapi/nightly-builds/
Tanya Yatskovskaya
SmartBear Community and Education Manager
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, the problem still happens on the 1.5.0 nightly build.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for checking this, kbw.
Our Dev team informed me that the investigation may take some time. Could you please start working with our Support Team? Also, please send them the problematic project as our R&D haven’t reproduced the issue in our test lab.
Tanya Yatskovskaya
SmartBear Community and Education Manager
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sure, I'll try to pare down the project while still retaining the problem, to make it easier to examine. Might take me a couple days before I can squeeze in the time to do that, before I can submit the support ticket.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FYI: This appears to be fixed in Ready API 1.7
