Re: Getting the QA Effort organised

Hi Zak and the QA team First, many thanks to Zak for trying to get the QA effort on some sort of heading. I won't quote the 3 emails, just add my comments to all of them here, the reference should be clear. >>Could everyone who is prepared to be actively involved with >>the PHP QA Team please send a confirmation to the list. Confirmed. For the record, I'm a C++/Java/Perl programmer, and of course PHP. I'm interested in how we test applications, especially in the Open Source context, i.e. without a formal stucture. To this end, I want to look into setting up some sort of automated testing. Anyone else interested in that area? I have a Linux server, running SuSE 6.3, Apache, MySQL and PHP3+4. I also have a Windows NT box running Apache and PHP 4. >>I know that I personally have difficulty in making time to >>contribute to the QA effort. I know the feeling. Trouble is, between projects, I have the time, and then as soon as another project hits, wham, I'm busy somewhere else. I think that is true for most of us. So this week I may be able to put 10-15 hours into it, next week, who knows... As far as modifying the bug reporting system goes, there have been some good ideas, but my feeling is, that unless someone will take it on and see it through to the finish, I feel we should work with what we have, anything else would be a distraction from the main work. So I see the first steps as being... 1. Get some way for us to have access to the bugs system, so that we can close bugs as we deal with them. Preferably with a way of grading them (open, closed, uncomfirmed and some text to explain why it is closed), but if that doesn't happen, lets just do it. 2. Lets aim to get 50 bugs closed starting now, and then take a look at what needs to be changed to the system. That way we will have more of a practical view of the issues. We will also get the feeling that we have done something. (50 is randomly chosen number...) Well, thats my .02 Euros worth. -- jalal --