If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

New types of sanity check.

RESOLVED WONTFIX

Status

()

Bugzilla
Administration
P4
enhancement
RESOLVED WONTFIX
17 years ago
3 years ago

People

(Reporter: CodeMachine, Unassigned)

Tracking

Details

(Reporter)

Description

17 years ago
At the moment we don't have all checks covered.

It would be nice to have various other sorts of checks.  The following come to mind.

1.  Uniqueness checks.  Currently I can see a uniqueness check for keywords but
nothing else.  Is it because these are enforced by MySQL and referentials
aren't?  If so we can probably forget about a lot of this at least until we have
database independence.  At least versions doesn't appear to have a primary key
specified.
2.  Check that 1 <= votes <= (votes allowed for this product for this bug).
3.  MIME type valid.
4.  Using the referential information, check the types of primary and foreign
key are identical.
5.  Compound referential checks, for milestones, components and versions are
present, but should probably be moved to being configured by data, like
CrossCheck.  I don't think at least products/defaultmilestone is currently
checked either.
6.  Milestone URL is a valid URL.
(Reporter)

Comment 1

17 years ago
We also should have existence checks - each product should have at least one
component, each product should have at least one milestone,  etc.
(Reporter)

Updated

17 years ago
Target Milestone: --- → Future
(Reporter)

Comment 2

16 years ago
Moving to new Bugzilla product ...
Assignee: tara → justdave
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: Bugzilla 2.10 → 2.13
Reassigning all of my "future" targetted bugs to indicate that I'm not presently
working on them, and someone else could feel free to work on them.
Reassigning all of my "future" targetted bugs to indicate that I'm not presently
working on them, and someone else could feel free to work on them. (sorry for
the spam if you got this twice, it didn't take right the first time)
Assignee: justdave → nobody

Updated

11 years ago
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Future → ---

Comment 5

11 years ago
I really wish this was split into multiple bugs and then this one was closed.
Keywords: qawanted
Priority: -- → P4

Updated

11 years ago
Keywords: qawanted

Comment 6

9 years ago
I'm not even sure this is needed at all.
Assignee: nobody → administration
WONTFIX per comment 6. File one bug per sanitycheck ID with use case and rationale.

Gerv
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.