Skip to content

Rhaptos Software Development

Personal tools
You are here: Home » Developer Blog » Jenn's DevBlog » Testing queue available for viewing

Testing queue available for viewing Testing queue available for viewing

Document Actions
Submitted by jenn. on 2005-05-05 14:16. DocumentationMaintenance
For a while now, the main testing status and to-do list have been available here on the software site.
The test queue gives the testing status of various developments, of whatever scale, from entity fixes to the Plone 2 migration. Anyone can go there to find out what's "ahead of them" in the queue, or how far I've gotten with testing something, or just the status of some specific bit of development they're not involved in.

The format is pretty freeform at the moment, but I'm formalizing it more as time passes. Eventually it could be joined with the task database, though I'm not sure we have the volume of development and fixes to require a full-blown integrated issue-and-code-tracking system. I think there's definitely a level of formality that's too much for us, and would just get in the way -- though I still have fond hopes of revamping the task system to track bugs by system component.

Re: Testing queue available for viewing

Posted by maxwell at 2005-05-05 20:14
I looked at your bug list, and had a response to one of the items in the "Fresh Bug List" and had a response to one of them (BTW, it would be neat if I could make comments directly on the list instead of here on the blog). In response to the question:

Why is "Connexions" separately underlined in "What Is Connexions" on the front page of the tour?

I can tell you that is doesn't have a separate underlining. It is just in italics, and for some reason, Mozilla doesn't treat linked italics the same way it treats linked non-italic text. If you look at the tour in IE, it doesn't have the same problem. I'm not sure what to do to fix the problem besides take out the italics altogether.

Re: Re: Testing queue available for viewing

Posted by jenn at 2005-05-06 10:05
Ah! Thanks. This is exactly why they're "fresh" and not, um, I dunno, "cured" bugs. My process would've been to go ask you about it, before bothering to write it up formally; you would've told me what you just told me; and I'd get rid of the bug without bothering the task system. I'll put a bit of text on the list saying for people to email me or come talk to me if they have input on those bugs.

(Darned openness! That was really just my own personal list...but I figured, we're being all documented and such, so I'll make it public. And look what happens: productive interaction. Hee hee.)
Developer Blog
« August 2008 »
Su Mo Tu We Th Fr Sa
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31            
2008-08-14
15:42-15:42 Signing on to Jabber from multiple locations
Categories:
Content (55)
Copyright (0)
Deep Code (3)
Development (200)
Markup (22)
Metadata (1)
Printing (7)
Style (9)
Testing (2)
Usability (6)