[TIMOB-6542] Android: Debugger - v8 - Breakpoint eval test case requires multiple "resume" clicks to see expected results
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Low |
Status | Reopened |
Resolution | Unresolved |
Affected Version/s | Release 1.8.0.1 |
Fix Version/s | n/a |
Components | Android |
Labels | branch-v8, tbs-1.8.2 |
Reporter | Eric Merriman |
Assignee | Unknown |
Created | 2011-12-09T12:13:23.000+0000 |
Updated | 2018-03-06T18:57:50.000+0000 |
Description
While running breakpoint eval test, starting with step 6, the tester must press "resume" and validate a variable and console output. A single press does not generally work, and the variables that were expected to increment by 2 are incremented by one. On the second press of resume, the expected results may be seen.
Steps to reproduce:
1) Create a new project in studio called debug_test
2) Move the js files form the debug test project in titanium_mobile_tests_internal
3) refer to the test plan at http://wiki.appcelerator.org/display/tp/Debugger+Test+Plan
4) Execute test case 1014
Result:
At step 6, the user must press resume twice where once is called for.
Expected:
A single press of resume get expected call frame and variable results
Resolved by TIMOB-6550.
Tested with 10.7.2, 10.6.8, Win 7 on 1.8.0.1.v20111214093905 Test is hitting a conditional breakpoint when the condition evaluates to false. First breakpoint goes to app.js: 16 when it should have skipped that since e=90 and not 95
This is related to the issue w/ breakpoints that have conditions.