Tools set:
1) Issue Tracker - Scarab: http://www.solitone.org/scarab_doc/index.html
Advantages: almost the same as Bugzilla, but much simpler and easier, does not contain all those extra useless features present in Bugzilla. Written in Java and the developers promise some really painless integrations with any kind of web-site.
Drawbacks: No plugin for Eclipse.
But at the same time - why do we need an issue tracker to be integrated into Eclipse? Historically all issue/bug tracking tools are web-interfaced applications, as for me - I can hardly imagine how I will deal with bug lists through thick-client Java apps.
2) Requirements manager - JRequire:
Advantages: Requirements management + code coverage tool in one pack! Feature-stuffed and the free version (community version) contains almost the same features as the commercial one! Eclipse plugin is available.
Drawbacks: Don‘t know yet, I was using different RM tools before, not this one.
3) Documentation storage - your current SVN repository.
Well, normally I‘m using MS Sharepoint site for these needs, but for the case of JFire project - one place for the sources and docs seem to be not such a bad alternative. I know several projects, who are using CVS or Visual Source Safe for storing all the project-related documentation. SVN will provide us such features as versioning and synchronous write-access for the stored items.
4) Functional/Regression tests for the thick client (Eclipse RPC application) - a really broad choices here, what are you using currently?
5) Functional/Regression tests for the thin client (web-interface) - Selenium: http://www.openqa.org/selenium/
Advantages: Unique, but simple methodology for testing web applications. Have heard many good feedbacks about this tool.
OK, this is my assessment for the tools set, waiting for your comments.
本站僅提供存儲(chǔ)服務(wù)，所有內(nèi)容均由用戶發(fā)布，如發(fā)現(xiàn)有害或侵權(quán)內(nèi)容，請(qǐng)
點(diǎn)擊舉報(bào)。
