We have a lot of issues which are open simply due to outstanding test coverage, including around 40 critical issues.

http://drupal.org/project/issues/search/drupal?status[]=Open&issue_tags_...

Having test-only issues at 'critical' makes it hard to see issues which are still outstanding in terms of active bugs, so I'm opening this single critical meta issue so we can review test coverage, (and this specific list) before release, and downgrade test-only issues to normal in the interim. That way we still don't release without reviewing and possibly fixing all those issues, but we don't dilute the criticals list either.

Have done the same thing for 'Needs documentation' - see #653068: Update documentation is incomplete.

Comments

moshe weitzman’s picture

moshe weitzman commented

Very good idea.

moshe weitzman’s picture

moshe weitzman commented

downgrading as per #653074: Review test coverage / outstanding tests before release

sun.core’s picture

sun.core commented
Priority: Critical » Normal
catch’s picture

catch
he/him
Primary language English
commented
Priority: Normal » Critical

No, this is critical so that other test coverage issues aren't. See the first post.

sun.core’s picture

sun.core commented

I know that our goal was a high test coverage, but I actually fail to see why missing tests should hold up a release.

catch’s picture

catch
he/him
Primary language English
commented

Same here. But this issue replaced over 50 critical ones which were hanging around. If we think test coverage is 'good enough' we could consider it reviewed now?

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Active » Closed (duplicate)

I think I've set really bad test issues with blatant holes (shortcut, images, etc.) as individually "critical" issues, so this can be marked as a duplicate IMO.