Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't run a whole test suite. Run test case by test case. Breakpoints work, but then test case may not continue well. #2

Closed
GoogleCodeExporter opened this issue Mar 17, 2015 · 1 comment
Closed

Don't run a whole test suite. Run test case by test case. Breakpoints work, but then test case may not continue well. #2

GoogleCodeExporter opened this issue Mar 17, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

That is due to complexity of Selenium control flow. It affects functionality 
provided by SelBlocksGlobal.

Highlighting of the selected test case and the actual selected (current) test 
case may be out of sync after your run a whole test case. If things don't 
behave as expected afterwards, select another test case and then select back 
the one you want to use.

Original issue reported on code.google.com by peter.kehl on 3 Feb 2014 at 8:47
@GoogleCodeExporter
Copy link
Author 

Fixed in version 0.78 of SelBlocksGlobal

Original comment by peter.kehl on 5 Feb 2014 at 9:14

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter