Closed
Bug 537997
Opened 15 years ago
Closed 15 years ago
Migrate spidermonkey tests into acceptance testsuite
Categories
(Tamarin Graveyard :: Tools, defect, P3)
Tamarin Graveyard
Tools
Tracking
(Not tracked)
VERIFIED
FIXED
flash10.2.x-Spicy
People
(Reporter: cpeyer, Assigned: cpeyer)
Details
Attachments
(1 file)
There has been a fair amount of tests written for spidermonkey that have been written since we initially migrated the tests over (2005?). The tests for features relevant to tamarin need to be migrated over.
Assignee | ||
Comment 1•15 years ago
|
||
This also includes tests for missing Array methods (filter, forEach,
map, some, every)
Status?
Flags: flashplayer-qrb+
Priority: -- → P3
Target Milestone: --- → flash10.1
Updated•15 years ago
|
Target Milestone: flash10.1 → flash10.1.1
Assignee | ||
Comment 3•15 years ago
|
||
Zipped up patch of all the migrated spidermonkey tests from js1_1 to js1_5. Still need to migrate portions of js1_6. There are also some unresolved issues with some of the tests that are noted in the testconfig.txt, will followup later of those.
Attachment #432696 -
Flags: review?(brbaker)
Updated•15 years ago
|
Attachment #432696 -
Flags: review?(dschaffe)
Updated•15 years ago
|
Attachment #432696 -
Flags: review?(dschaffe) → review+
Comment 4•15 years ago
|
||
Comment on attachment 432696 [details]
Spidermonkey tests js1_1 to js1_5
I ran the tests ok locally. we are adding 400 tests and should be careful we are not adding a lot of time onto the slower platforms. on my macbook went from 2m to 2m 30s but on winmo and android each additional test file adds times.
Assignee | ||
Comment 5•15 years ago
|
||
pushed to redux changeset: 4170:0c775f80c41f
Slow running tests have been marked to only run in the deep phase. Any individual bugs with tests should have new bugs filed.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Attachment #432696 -
Flags: review?(brbaker) → review+
Assignee | ||
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•