Establish Testing and Release Procedures
Posted by Digitalxero on 2009-07-13 02:24
For those of you who dont know me, I am Dj Gilcrease. I am the one you can blame all the issues of OpenRPG since version 1.7.x until version 1.7.7 on. And 90% of those issues could have been eliminated if I had (4 years ago) taken the advice of Tom, and a few others of the original Devs and committed to testing every change before pushing it out to users.
My argument was always, "Bugs get found much faster by the masses then by me testing alone". Now two years after having dropped the ball in the middle of a major change to openrpg and seeing the effect that it has had on the community and also from 2 years of experience in working on mission critical software for companies paying 200k+ per year for Service Level Agreements. I have a much better idea of how testing works and what needs to happen before something gets pushed to the masses.
Now my argument of the masses find bugs faster is still valid, but they need to be knowledgeable, and willing participants in such mass testing. So along those line anyone who is willing to help out, I am in the process right now of establishing OpenRPGs new release protocol that will guarantee a minimum level of quality for each release. Head over to http://www.assembla.com/spaces/openrpg/tickets/47-Platform-support-and-Dependency-Tes ting and read though the tests lists and the listed platforms & dependencies.
If there are additional tests you would like to see performed before a release detail the test procedure and what qualifies as a pass or fail. If you are willing and knowledgeable enough about your chosen operating system to run these tests, please do and provide feedback on the process. Since the process is still being finalized I am not looking for pass/fail reports just yet (Though do feel free to fill out a bug report if a test fails for you) what I am looking for is how the process could be improved and modified to reestablish a quality assurance within the community so they are not afraid to upgrade to the newest version.
My argument was always, "Bugs get found much faster by the masses then by me testing alone". Now two years after having dropped the ball in the middle of a major change to openrpg and seeing the effect that it has had on the community and also from 2 years of experience in working on mission critical software for companies paying 200k+ per year for Service Level Agreements. I have a much better idea of how testing works and what needs to happen before something gets pushed to the masses.
Now my argument of the masses find bugs faster is still valid, but they need to be knowledgeable, and willing participants in such mass testing. So along those line anyone who is willing to help out, I am in the process right now of establishing OpenRPGs new release protocol that will guarantee a minimum level of quality for each release. Head over to http://www.assembla.com/spaces/openrpg/tickets/47-Platform-support-and-Dependency-Tes ting and read though the tests lists and the listed platforms & dependencies.
If there are additional tests you would like to see performed before a release detail the test procedure and what qualifies as a pass or fail. If you are willing and knowledgeable enough about your chosen operating system to run these tests, please do and provide feedback on the process. Since the process is still being finalized I am not looking for pass/fail reports just yet (Though do feel free to fill out a bug report if a test fails for you) what I am looking for is how the process could be improved and modified to reestablish a quality assurance within the community so they are not afraid to upgrade to the newest version.
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Openrpg is powered by Assembla.
0 Comments