# Bugzilla category for test case bugs?

- Thread: https://externals.io/message/30063
- Original archive: https://news-web.php.net/php.internals/30063
- Started by Zoe Slattery on 2007-06-05T09:29:04+00:00
- Messages: 3
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #30063 — Zoe Slattery — 2007-06-05T09:29:04+00:00

URL: https://externals.io/message/30063#30063

Hi all
Would it be possible to have a Bugzilla category for test case bugs?  
The only alternative seems to be to raise a bug against the 
implementation - which doesn't seem quite right.

Zoe Slattery
IBM

---

## #30065 — Pierre — 2007-06-05T09:38:27+00:00

URL: https://externals.io/message/30063#30065 · In reply to: #30063

>
> Hi all
> Would it be possible to have a Bugzilla category for test case bugs?
> The only alternative seems to be to raise a bug against the
> implementation - which doesn't seem quite right.

Why not simply put them in the related category? For example GD for a
problem in a GD test. With an extra category, I will simply not see
any bugs related to my extension tests, even when I'm fetching the
'GD' category bugs.

What would rock is a bug "type" field. A bug can be GD and Testing
related, or Ming and Documentation.

--Pierre

---

## #30070 — Zoe Slattery — 2007-06-05T14:45:27+00:00

URL: https://externals.io/message/30063#30070 · In reply to: #30065

Pierre wrote:
> 
> > […]
>
> Why not simply put them in the related category? For example GD for a
> problem in a GD test. With an extra category, I will simply not see
> any bugs related to my extension tests, even when I'm fetching the
> 'GD' category bugs.
That's reasonable. The reason that I asked was that all I'm doing is 
writing functional tests - so, for example - if I make a mistake in a 
functional test for "Filesystem" I don't necessarily see why the 
developer working on Filesystem should have to look at it, or spend 
their time fixing it. By the way, this came up because a colleague found 
a mistake in a test and couldn't work out the right way to raise a defect.

I also noticed that there are separate categories for Documentation 
defects - so it seemed to me to be consistent to have one for tests.

I'm happy to ask people to  with raise  them against the implementation 
- I just didn't want to cause unecessary work for the core developers. 
Of course I'm *hoping* that there won't be enough defects in the test 
cases to cause anyone major headaches :-)
>
> What would rock is a bug "type" field. A bug can be GD and Testing
> related, or Ming and Documentation.
> --Pierre