QA task list

I would rather have a matrix of the wishes & bugs next than an RTE matrix at this time. My QA release task list is somewhat as follows:

  1. Matrix of bugs & wishes (& doc. needs)
  2. State diagram reduced to test cases for an Internet Cafe identity problem
  3. RTE test case matrix

Tags

  1. agile
  2. testing

Comments


Mark de LA says
The tagged bug lists also tag a lot of crap that is not necessarily useful. It would be a good thing to crisp some of that up in a short title.

Mark de LA says
They also come out in LIFO order which may or not be the best order to work on them. That's why I did the priority/severity tagging which you rejected.

Mark de LA says
I grokked that a long time ago. THe point is you have to navigate that structure to find anything out like how many bugs are there, what are the top 10 that should be fixed, how much time etc,

Seth says
seth 2005-11-04 06:51:34 1865
Mark 2005-11-04 06:45:30 1865
They also come out in LIFO order which may or not be the best order to work on them. That's why I did the priority/severity tagging which you rejected.
there is no fixed order to work on them, lifo or fifo.  one works on them by project name. 
right now i am primarialy working on _tags but to make some of the things that i am doing there become more apparent and work for the users i have also developed a bit in display or even display,navigation or perhaps what i am really working on right now is display,hierarchy

Seth says
Mark 2005-11-04 06:47:54 1865
The tagged bug lists also tag a lot of crap that is not necessarily useful. It would be a good thing to crisp some of that up in a short title.
then it should be cleaned up

Seth says
Mark 2005-11-04 06:45:30 1865
They also come out in LIFO order which may or not be the best order to work on them. That's why I did the priority/severity tagging which you rejected.
there is no fixed order to work on them, lifo or fifo.  one works on them by project name. 

Seth says
Mark 2005-11-04 06:37:21 1865
I grokked that a long time ago. THe point is you have to navigate that structure to find anything out like how many bugs are there, what are the top 10 that should be fixed, how much time etc,
it may be very useful to make a functional matrix.  thing to realize is that one needs to keep it up to date.  if there is a bug count in some particular catagory, who is going to update that number when the bugs get fixed, or when more bugs are added. 

.... hmmm

perhaps we need a wiki reference to count things in a room

[count .... any wiki reference ... ]

Seth says
source:
1. Matrix of bugs & wishes (& doc. needs)
That exists now as tag rooms.  Personally i dont need anything more than we already have.  But to make a matrix of that, you simply organize an item refering to the various tag rooms in some analyis of it.  Here might be a sample of one (of the many) ways to display the matrix.
... do you grok ?

Mark de LA says
When I think about it a bit more, I will write up something in the group agile - the agile community doesn't address bugs that much because the methodology isn't supposed to release bugs. Tests are made before the functionality is coded. More about this in that group.

Mark de LA says
Also, I can't tell whether all the things prefixed with a period have been incorporated or not. My intention with this item was to consolidate, organize & list. I don't think you grok the situation. It is like the problem we had trying to get linear documentation out of CyberMind. I'm sure you will eventually want to do something different when you get more than one programmer.

Mark de LA says
Then there are also all those ^ tags that are or NOT integrated into the new system. If you have one matrix to refer to as "THE" list of bugs, wishes or whatever then you don't have to chase around cyberspace to find all the particulars of what's on it.

Seth says
Mark 2005-11-04 07:18:15 1865
Also, I can't tell whether all the things prefixed with a period have been incorporated or not. My intention with this item was to consolidate, organize & list. I don't think you grok the situation. It is like the problem we had trying to get linear documentation out of CyberMind. I'm sure you will eventually want to do something different when you get more than one programmer.
one can spend lots of busy time orginizing, listing, and analyzing things.  it does not imporve the things.  if you want to spend time on it, spend time editing the items so that they show correctly what the bug or wish actually is, and if it is a real bug, how the bug can be reproduced.  that, and that alone, will actually improve our situation. 

Seth says
Mark 2005-11-04 07:30:15 1865
Then there are also all those ^ tags that are or NOT integrated into the new system. If you have one matrix to refer to as "THE" list of bugs, wishes or whatever then you don't have to chase around cyberspace to find all the particulars of what's on it.
what i have been doing is whenever i encounter one of those older style qa tags, i edit the tag.  i had assumed that you would do that as well.  some of these tags are in private groups that one needs to login before one can effect the tag.  eventually i will either log into that group or use my domain power to rename these tags.

Mark de LA says
Well, I don't just encounter them. I think it takes an overt act to destroy them. That's triage & takes a little time. I have been focusing my attention on what the thing is & how can I use it to solve a problem or do something useful besides publish my vanities of thought.

Mark de LA says
Sorry about the pronouns, but the item comments grows geometrically if we continue to quote eachother in a linear chat. (;-))

Seth says
Mark 2005-11-04 08:11:37 1865
Well, I don't just encounter them. I think it takes an overt act to destroy them. That's triage & takes a little time. I have been focusing my attention on what the thing is & how can I use it to solve a problem or do something useful besides publish my vanities of thought.
that is fine, i have no problem with what you are doing .  but i do "just encounter" them as i do research in the system whether it is research into what is wrong in a particular program area or research into how tags are working for me or whether they are a bit tedious to get instantly what i want out of them.  tags are the way i remember things now ... i have lost my mind

Mark de LA says
I don't know how the nested quoting is affecting the db size, but maybe we should revisit the notion of something like slashdot does.

See Also

  1. Thought Agile Dilbert Cartoon with 161 viewings related by tag "agile".
  2. Thought What if there were no stars? with 26 viewings related by tag "agile".
  3. Thought about: my webid in Kingsleys dataspace with 3 viewings related by tag "testing".
  4. Thought Using FastBlogIt with Agile Processes with 3 viewings related by tag "agile".
  5. Thought Bug in title field with 2 viewings related by tag "testing".
  6. Thought Your intrepid blogger with 1 viewings related by tag "testing".
  7. Thought Is this a bug? with 0 viewings related by tag "testing".
  8. Thought Google spreadsheet soon with 0 viewings related by tag "agile".
  9. Thought i posted this item without a signon after posting an anonymous comment with 0 viewings related by tag "testing".
  10. Thought Experiments online with 0 viewings related by tag "testing".
  11. Thought test post with 0 viewings related by tag "testing".
  12. Thought Bugs to fix on fastblogit after the move: with 0 viewings related by tag "testing".
  13. Thought Fitnesse with 0 viewings related by tag "testing".
  14. Thought Scrum for M$ with 0 viewings related by tag "agile".
  15. Thought Agile Processes with 0 viewings related by tag "agile".