Hi, > Another idea has been initiated (or resuscitated) at the council > meeting: to implement a tool for collecting and analyzing results of the > automated testruns. As alredy mentioned by Joos, we (Joost, Laurent > Godard, Jörg Sievers, Thorsten Bosbach and me) had a a first > "brainstorming" session about that. As this idea has been filed as > Google Summer of Code Application, we should have a good starting point. > So we know about a similar tool, that is used inside Sun (we have ben > able to havea short look at the tool). Unfortunately, the technology > cannot be used outside Sun (as ist is proprietary and depends on the > local environment). But Sun agreed, that the tooling will be documentend > a a mentor was available. (In fact some parts are already documented). > We do have also a solution for the hosting at hand. So what we really > need is someone who is volunteering to implement this. Laurent is going > to see, if volunteers can be recruited at a nother project (the project > is about automated testing of OpenSource Software in general .. and > testing OOo would be some kind of prototype). > But If we have interested people here at the project, please raise your > hand ;-)
first of all let me introduce myself. (Don't know if I've already done that to this list) My names Helge Delfs and I'm working at SUN as an automated tester within the Team around Joerg 'Jogi' Sievers and Thorsten Bosbach. I'm responsible for automated tests of the writer component and I've developed some tooling for our internal QA-Project. And thats the point why I'm replying to this mail :-) I developed the concept and code of the QA-Statuspage. (our internal name for the tool Andre mentioned to collect and analyze results of automated tests)...must be the reason why I picked up to be the mentor of the GSoC-Application. ;-) To cut a long story short let me spread some details on how we (Thorsten Ziehm, Jogi, Thorsten B. and me) think to support this tool from the beginning to give it a good start. If someone was found to volunteer implementation of this project we will first hand over the complete database model we use for our internal project. As this database was grown during the whole developing-process we thought it would be a good idea, because it gives an overview of the data that should be collected. As a matter of course we will support you with know-how about how to collect the data in case of need. Hope this are good news and help to give some more motivation for potential developers of this tooling ;-) -- Regards Helge --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
