XPCOM Proxy Tests need to be expanded and improved

NEW
Unassigned

Status

()

Core
XPCOM
9 years ago
8 years ago

People

(Reporter: wolfe, Unassigned)

Tracking

({mobile})

unspecified
ARM
Windows Mobile 6 Professional
mobile
Points:
---
Bug Flags:
wanted-fennec1.0 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

9 years ago
Created attachment 362074 [details] [diff] [review]
v1.0 patch

Right now, XPCOM Proxy testing is very weak and did not spot an invalid return code being passed back under WinCE.

These tests need expanding and revising in order to do better regression testing as well as assisting porting to new environments.

This first attachment is an attempt at creating tests that run from 1 to 10 arguments of various types.  These simple tests just add all the arguments together and return the result in the first argument - and then return a specfic code for both result AND return code.

This first attachment is also in the middle of revising the tests so that nothing is printed out via "printf()" if a test succeeds, but a warning is printed out if a test fails.

Work remains to propogate failure codes out to a exit code, so that this testing can be run automatically to further assist in unit testing efforts.
Flags: wanted-fennec1.0+
You need to log in before you can comment on or make changes to this bug.