Add continuous validation test capability




14 years ago
6 years ago


(Reporter: bugreport, Unassigned)


Dependency tree / graph



(1 attachment, 1 obsolete attachment)

This needs a bit of cleanup, but it is possible to wrap the template toolkit in
a wrapper that calls an html validator.  

We should definitely do this on certain installs on landfill.

There is a validator at that is easy to
build and install.
   1) Move valudation function to (no reason to involve
   2) Make location of validator executable configurable (localconfig, param, or ??)
   3) Add the URL used to trigger the failing template to the logged information.
   4) Save an exerpt of the HTML in the area of the first failure.
   5) Disable the WRAPPER function altogether if validation is not in use.

Then, this is actually non-invasive enough that it could land.

Priority: -- → P3
Target Milestone: --- → Bugzilla 2.22
Blocks: 237847
Blocks: bz-validhtml
No longer blocks: 237847
Summary: Add contunuous validation test capability → Add contiunuous validation test capability
Assignee: zach → bugreport
Attachment #198124 - Attachment is obsolete: true
Attachment #198413 - Flags: review?(LpSolit)

You can try this on landfill using "/opt/validator/bin/validate" or
"/opt/validator/bin/validate --verbose" as the value for the "validator" parameter.
Comment on attachment 198413 [details] [diff] [review]
Non-invasive patch no longer exists
Attachment #198413 - Flags: review?(LpSolit) → review-
The trunk is now frozen to prepare Bugzilla 2.22. Enhancement bugs are retargetted to 2.24.
Target Milestone: Bugzilla 2.22 → Bugzilla 2.24
Summary: Add contiunuous validation test capability → Add continuous validation test capability
Note that I now use the 'HTML Validator' extension of Firefox to track HTML errors. Maybe that's enough as you cannot use here anyway.
This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2
Assignee: bugreport → zach
Target Milestone: Bugzilla 3.2 → ---
Assignee: zach → testing
You need to log in before you can comment on or make changes to this bug.