search

refactoror / SelBlocks

SelBlocks extension for Selenium IDE
10 stars 7 forks source link

Unhandled try..catch from one test case affected try..catch in the next test case #12

Closed peter-lyons-kehl closed 9 years ago

peter-lyons-kehl commented 10 years ago

Hi Chris.

The background is the same as for https://github.com/refactoror/SelBlocks/issues/11. However, this issue is a bit more complicated. It involves running two test cases in sequence (but running either of them right after starting Se IDE works with no visible problem).

The first test case is https://code.google.com/p/selite/source/browse/selenese-tests/try_with_unmatching_catch_at_top_level_case.html?repo=sel-blocks-global (for download: https://sel-blocks-global.selite.googlecode.com/git/selenese-tests/try_with_unmatching_catch_at_top_level_case.html). The second case is https://code.google.com/p/selite/source/browse/selenese-tests/try_without_catch_at_top_level_case.html?repo=sel-blocks-global (for download: https://sel-blocks-global.selite.googlecode.com/git/selenese-tests/try_without_catch_at_top_level_case.html).

After running that sequence, Selenium IDE stays in running mode; Browser Console shows 'tryState is null' in selblocks.js, line 788. My fix was https://code.google.com/p/selite/source/detail?r=0c3be2ee6aee63a87de0ab5f609f7e2f9da85ef7&repo=sel-blocks-global.

peter-lyons-kehl commented 10 years ago

FYI I've moved those test cases. Now they are at https://code.google.com/p/selite/source/browse?repo=sel-blocks-global#git%2Fselenese-tests-negative > try_with_unmatching_catch_at_top_level_case.html and try_without_catch_at_top_level_case.html.