Closed Bug 368097 Opened 13 years ago Closed 4 years ago

XUL Widget Tests

Categories

(Toolkit :: XUL Widgets, defect)

x86
macOS
defect
Not set

Tracking

()

RESOLVED WONTFIX

People

(Reporter: enndeakin, Assigned: enndeakin)

References

Details

Attachments

(1 file, 1 obsolete file)

This is about checking in the XUL widget test suite I've been working on. Currently, I'm going to put them in toolkit/tests and can run during the make check phase.
Nice. How do they run?
It should run by opening a browser and running through the tests for each widget. It works in the same way as the reftests do.

It doesn't output any pass/fail state to the console though as I'm not sure what should happen there. It does display a table of green pass and red fail rows.

Attached patch Current tests I have written (obsolete) — Splinter Review
This adds tests to test the following widgets and xul features:
  datepicker, key, scale, stringbundle, textbox, spellchecking textbox,
  timepicker, notificationbox, menu, menu buttons, trees and templates

The patch in bug 364508 is needed for the tests to work. Some subtests don't work if the window isn't raised, and three of the spellchecking subtests don't work on Windows.

To run the tests:
  cd [outputdir]/toolkit/tests
  make lcheck
Assignee: nobody → enndeakin
Status: NEW → ASSIGNED
That patch doesn't include happy.png (naturally, since it's binary)...
So when I run these, it runs the "Menu Toolbar Button" tests what looks like partway (according to the progress meter) then stops...  Is that expected?

Also, given a test failure is there a reasonable way to view that test?

Finally, there are 0 tests for toolbar, images, etc?  Or am I doing something wrong?
The patch here for the tests are works in progress, so only the elements listed in comment 3 have tests.

> So when I run these, it runs the "Menu Toolbar Button"
> tests what looks like partway (according to the progress meter)
> then stops...  Is that expected?

No, but that was an issue on Windows. It's possible I made the patch before I fixed that issue.
These tests are old and mostly either have been added or have equivalents added.
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.