Forum OpenACS Q&A: Improving Test Reporting

Posted by defunct defunct on 10/04/02 06:45 PM

I've been having some interesting discussion about the SDM and how to
avoid cluttering/overburdening it.

Anyway, I'm just trying to think if there's anything we might do,
thats simple, in the interim to help alleviate it.

What about if I add in table or two to the certificate system where
people can record a bug found during pre-beta testing. Then when we do
post-beta testing, we compare the previous set to ensure they've been
fixed. Only if then they haven't been fixed do we log to the SDM?

Any thoughts on that?

2: Response to Improving Test Reporting (response to 1)

Posted by Jeff Davis on 10/04/02 07:07 PM

We should just put them in one place. One of the biggest problems with
openacs is data and docs are all over the place.

As it stands, I know there is a bug tracker for bug tracker but I always forget where it is, I know there is one for dev.openacs.org but
never bother to look at it, I know there is one for dotlrn
somewhere (or I think there is, actually, I never looked for it).
There are bugs in all of them I could fix but I just don't see them.

Another place to put bugs is probably not the right answer. Beter would probably be put them in sdm and we can manage the clutter via
states (like bugs come in as "new bug" and get promoted to confirmed
or assigned or taken or something like that once a developer has a
look at it and thinks they can fix it).

3: Response to Improving Test Reporting (response to 1)

Posted by defunct defunct on 10/04/02 07:11 PM

Sure.. I was only thinking as an interim measure while we come up with something better.