Testing Debate

registered · Site Admin Joined: Aug 22, 2007 Posts: 1775

montego wrote:

You haven't seen anything yet! Wait until you see the brand new (yes... "new") CMS being worked on... *sorry for the teaser* Smile

I hope you are test the new version better as the current. I've only started a year after the publication of version 2.5 with using this version and have found a lot of mistakes that could have been avoided by testing. *sorry for the facts*

registered · Posted: Sat Mar 23, 2013 8:20 am

neralex, the real facts are that we took a PHP-Nuke with over 10,000 PHP errors/warnings, compliance issues, bugs, security problems, etc. and turned it into a CMS that people can depend upon to stay up, operational, fast, and secure. Not a bad track record on the "facts" in my opinion. But, that isn't what this thread is about, so let us leave our differences of opinion right here.

Posted: Sat Mar 23, 2013 3:43 pm

montego you know exactly what i mean. Smile

Posted: Sun Mar 24, 2013 5:45 pm

neralex, no, actually I do not. You said "found a lot of mistakes"... I guess everyone's definition of "a lot of" is different. I would say finding and fixing >10000 issues from PHP-Nuke as "a lot of". Has the community found additional ones, including issues we have caused ourselves? Sure. You won't find a software package that is ever perfect in its release. But, relatively speaking, I'd say our track record has been really good over the years as we've really been cleaning up the original mess of code we inherited.

I have broken this "thread" out from the original as it added no value to that discussion.

Posted: Sun Mar 24, 2013 6:47 pm

montego, only because you have fixed in the past a lot of errors, is it today not more important to test new scripts? I have start one year after the release of RN25 and you know exactly what i have found in this version one year later. You know the list and the most of all these fixes in RN251 are real mistakes based of not tested areas. Alone the display bug in the forums module shows this what i mean very directly. The next curveball was the issue with the not working css styles with the editor or better with kses.php, the email send bug from the sentinel etc - all these things were new in RN25. It seemed for me as if RN25 were published untested. These errors were obvious and none of you have noticed it within a year. Such embarrassing mistake should not happen in this system. Not more and are no less I wanted to say.

registered · Site Admin Joined: Jun 04, 2004 Posts: 6437

neralex, if you're volunteering to test, that's wonderful. I'm sure everyone would appreciate that. If not, well, we appreciate what you've already pointed out. Montego isn't saying that we aren't concerned with testing or fixing errors, only that the significance of the issues pales in comparison with where we started (i.e. we have a history of correcting issues). We agree that there is room for improvement.

The team tries to resolve all known errors as quickly as possible. No one claims that RN is perfect, so I don't understand your need to highlight these issues again. I think Montego's point is essentially the same as mine: in over 25 years of professional software development with many companies large and small, I haven't worked with a more professional and dedicated team, especially considering we're all volunteers taking time from family, regular jobs and other interests and working with a geographically distributed team. Your view might be different, of course, and you are welcome to it. I just don't see how continuing this is helpful - for you or anyone else.

Posted: Fri Mar 29, 2013 2:45 pm

kguske, i know that all but i have not open a new thread, i have not start a new discussion about it. I have only written one statement - not more. Maybe you should try to get ready for the next (tested) release and not to make open threads for things, they we all know. I don't like postings "our news version is .... (bla bla bla)" Yes, i'm a user of this cms and yes i will see results - not more!

Posted: Fri Mar 29, 2013 3:02 pm

Again, thank you for pointing out the issues previously. Since there is no value to this thread, I'll lock it.