Gather XUL regression tests to viewer test suite

RESOLVED WORKSFORME

Status

()

P2
normal
RESOLVED WORKSFORME
19 years ago
8 years ago

People

(Reporter: waterson, Assigned: jrgmorrison)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [dogfood-])

(Reporter)

Description

19 years ago
From a private email exchange with karnaze/hyatt:

> > The general problem is that there are no  (there is only one xul test
> > and it may have a tree) table regression tests that have trees. To
> > prevent this from happening in the future, some tests need to get
> > added to the table regression tests. I think Hyatt mentioned some
> > tests before, but I can't remember.

> In layout\html\tests\table there are subdirectories core, bugs,
> marvin, viewer_tests, other. Each of these has a file called file_
> list.txt. To add a new test, select the appropriate subdirectory,
> put an entry in file_list.txt and put the test page in the
> subdirectory. To run the tests, "rtest baseline" will create a
> set of regression data files and "rtest verify" will compare against
> them. There is also an rtest.bat in the parent directory which
> cycles through the subdirectories.
>
> That is for windows. For Unix,  Kipp added corresponding shell
> scripts, but I have never used them.

Let's get this done! I have a couple of tree test cases, evaughan has a pile of
box test cases, i'm sure pink has toolbar stuff.

Updated

19 years ago
Summary: [dogfood] gather XUL regression tests to viewer test suite → [dogfood] Gather XUL regression tests to viewer test suite
Target Milestone: M12

Comment 1

19 years ago
Sounds good, let's target getting this done in M12. cc'ing folks mentioned.

Comment 2

19 years ago
When doing this, please create new subdirectories tree, box, etc.

Updated

19 years ago
Whiteboard: [PDT-]

Comment 3

19 years ago
This is a very good idea, but not mandatory for dogfood.  But impt to do.
Putting on PDT- radar.

Updated

19 years ago
Priority: P3 → P2
Whiteboard: [PDT-] → [PDT-] [PT+]

Comment 4

19 years ago
We could get to dogfood without it, sure, but I think we'll get there sooner,
and keep the quality up there better by doing this.  I don't know why this was
even marked dogfood, it is not a feature or a defect, just good engineering.
Leaving target M12, P2

Updated

19 years ago
Assignee: trudelle → sdagley

Comment 5

19 years ago
assigning to sdagley

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 6

19 years ago
spam: changing qa contact from ckritzer -> paulmac for xul bugs

Updated

19 years ago
Whiteboard: [PDT-] [PT+] → [PDT-]
Target Milestone: M12 → M13

Comment 7

19 years ago
moving to m13

Updated

19 years ago
Target Milestone: M13 → M14

Comment 8

19 years ago
moving to m14

Comment 9

19 years ago
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL

Comment 10

19 years ago
Doesn't meet the BETA1 criteria, moving out of M14
Target Milestone: M14 → M15

Comment 11

19 years ago
Putting dogfood in the keyword field.
Keywords: dogfood

Updated

19 years ago
Summary: [dogfood] Gather XUL regression tests to viewer test suite → Gather XUL regression tests to viewer test suite

Comment 12

19 years ago
changing QA to jrgm. John, I doubt we're going to worry much about this in the 
current release, but could you own this issue in genreral, going forward?
QA Contact: paulmac → jrgm

Comment 13

19 years ago
Clearing the target milestone and assigning the bug to QA as I don't know who 
owns the test suite but I do know it isn't me.
Assignee: sdagley → jrgm
Status: ASSIGNED → NEW
Target Milestone: M15 → ---
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED

Comment 14

19 years ago
Putting on [dogfood-] radar.
Whiteboard: [PDT-] → [dogfood-]

Updated

18 years ago
Keywords: nsdogfood-

Updated

18 years ago
Keywords: nsdogfood

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
we have XUL tests now, automated even.
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.