Integrate FCKeditor test suite

NEW
Unassigned

Status

()

P5
enhancement
11 years ago
4 months ago

People

(Reporter: jruderman, Unassigned)

Tracking

Trunk
x86
Mac OS X
Points:
---
Bug Flags:
wanted1.9.1 ?
in-testsuite ?
in-litmus ?

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
We break FCKeditor fairly often.  How about making it part of our automated tests?

http://www.fckeditor.net/license
http://dev.fckeditor.net/wiki/Testing

Comment 1

10 years ago
This would be some good automated testing considering recent bug 453462 and all the others times this happenned... Fckeditor is widly used.
Flags: wanted1.9.1?
Flags: in-testsuite?
Flags: in-litmus?

Comment 2

10 years ago
Fixed by + flag in bug 453462
Depends on: 453462
Flags: wanted1.9.1?
Flags: in-testsuite?
Flags: in-litmus?

Updated

10 years ago
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
That doesn't fix this. All that did was add one test for one specific case that we broke. Actually adding FCKeditor's testsuite would ensure that we don't break anything that FCKeditor uses, which was Jesse's point in comment 0.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → NEW

Updated

10 years ago
Flags: wanted1.9.1?
Flags: in-testsuite?
Flags: in-litmus?
This sound like a good idea!
Component: Testing → DOM
Summary: Consider integrating FCKeditor test suite → Integrate FCKeditor test suite
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.