[TIMOB-6546] Android: Debugger - v8 - Args test case contains many unexpected variables
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2011-12-14T16:38:47.000+0000 |
Affected Version/s | Release 1.8.0.1 |
Fix Version/s | Sprint 2011-49, Release 1.8.0.1, Release 2.0.0 |
Components | Android |
Labels | branch-v8 |
Reporter | Eric Merriman |
Assignee | Marshall Culpepper |
Created | 2011-12-09T12:40:34.000+0000 |
Updated | 2014-06-19T12:44:10.000+0000 |
Description
While running the Args test, after step 6, many unexpected global and local variables appear in the variables pane. See attached image.
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 1021
Result:
Many unexpected variables
Expected:
'local' variables (a, b, c, i, arguments)
'global' variables (array, button, exception, encode, win, argtest, evt, x)
Attachments
File | Date | Size |
---|---|---|
variable.jpg | 2011-12-09T12:40:34.000+0000 | 235150 |
Should be fixed with variable filter fix.
When testing this with Ti Mob SDK build 1.8.0.1.v20111214093905 I noticed that after expanding arguments after step 7, there were extra variables included when there shouldn't have been any. Theses variables are: callee, length, _proto_ and constructor
Tested with 1.8.0.1.v20111214093905 on Win7, Lion. The extra arguments is not a bug, will open a new bug to track parity