Source Code Quality Gate
 

Alright, let’s flush this out, see if the dev's can have some input on this.

What quality gates are in place for new code?

What quality gates are in place for the community submitted code?

How can we (we being the community) improve the quality of the source code being A. Developed and B. including into the office release.

Possible ideas.... Coding standard maybe?

110% open to suggestions

- froglok

Yikes, Quality... while I definitely agree, the idea scares me. It's what I do almost 60 hours a week. :)

Ouch! 60 hours a week! eep indeed.

hehe

Do you work as a QA? Woudl eb godo to have a source of input from a professional QA'er

- froglok

Oh I definitely offer my opinion around here plenty, whether asked or not. Anything I can do that I have time for, indeed. FNW once introduced me to the test plan for EQEmu. Not sure if you know about that yet. I think it's hosted on PEQ, using the testlink product. Can't remember the URL exactly.

Hi John,

I had no idea we had any sort of test plan for EQEmu at all.

This sort of stuff needs to be made public so we all can see it :D

Ill see if I can chase itup with FNW or if FWN can post the link here, it woudl greatly help :D

- froglok

I'm sorry, I lost the link a long time ago, but it is indeed cool. Even for non-dev, non official QA types, users can review the "test plan" on how to test a specific component. It was quite nice. I cannot say anyone used it to record test results, but at least if you wanted to test a "attack code", it was laid out how to do so.

There's also test plans on the wiki as well, but those are all fairly outdated.

*nods*

Then these are soemthign we need to revive, review and reissue then. Once again we need input from the dev team :\

- froglok