- January 8, 2005
- 15
- 0
I think we need to come up with a way for testers to post bugs for consideration before they get logged. I have tried reporting bugs in the forums and get no response so I don't know whether the post is being looked at, ignored or just not read.
Also, other developers need to be able to see what has been entered so as not to duplicate entries. They should have the option to add more information to the post, but it should not turn into a free for all like the forums generally seem to do.
A better method of communication should be established between developers and certified testers. It is not always possible to meet on IRC and even if it is it may not be a good time to test things out there and then. (Wives and children getting in the way again )
If any or all of the above is already available then the problem is with communication. I would love to help with testing but the developers need to identify how they want the testing to be done, it is your project after all.
Finally, in the same way MP is being developed in peoples spare time it should be remembered that that is how it will be tested. You are not going to get a team of regimented tester reporting bugs in a consistent manner 24/7 using a rigorous test plan, but if you define the process by which you want us to do things it should at least be a step in the right direction.
Just my opinion, hope it helps
Also, other developers need to be able to see what has been entered so as not to duplicate entries. They should have the option to add more information to the post, but it should not turn into a free for all like the forums generally seem to do.
A better method of communication should be established between developers and certified testers. It is not always possible to meet on IRC and even if it is it may not be a good time to test things out there and then. (Wives and children getting in the way again )
If any or all of the above is already available then the problem is with communication. I would love to help with testing but the developers need to identify how they want the testing to be done, it is your project after all.
Finally, in the same way MP is being developed in peoples spare time it should be remembered that that is how it will be tested. You are not going to get a team of regimented tester reporting bugs in a consistent manner 24/7 using a rigorous test plan, but if you define the process by which you want us to do things it should at least be a step in the right direction.
Just my opinion, hope it helps