Could be useful to structure the content of our discussions concerning testing in teams, automation tools, etc. in a Wiki page. It will be simpler to have an overview of all the processes involved.<br><br>Regards,<br>Clem<br>
<br><div><span class="gmail_quote">On 1/24/07, <b class="gmail_sendername">richie</b> <<a href="mailto:richie@vtiger.com">richie@vtiger.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Guys, you have to help me figure this out.<br>
What about the other sages out there. Any ideas please?<br>
<br>
BTW, AdventNet's QEngine can be used for the testing and regression
purposes. If someone is willing to share some sweat on it, it will do
the product a world of automation-good.<br>
<br>
Torsten, I think the trac holds what all you ask for in terms of the
fields that you require. I guess, we can do a hand-holding there for
you to come to pace with it.<br>
Let me know please.<br>
<br>
Fathi, could you tell how we can add custom fields to the trac please?<br><span class="sg">
<br>
<b>Richie</b></span><div><span class="e" id="q_110540232ae59250_2"><br>
<br>
Torsten Zenk wrote:
<blockquote cite="http://mid45B66FE8.9000301@gmx.net" type="cite">
<pre>Hi Richie,<br>maybe i can point out how i think it could work very smoothly:<br><br>If a group of moduletesters (MTG) has 2- 3 Testers (1 on each plattform <br>should be perfect), those 3 communicate via email or maybe even in a
<br>Testingforum if you could centrally set one up.<br>The MTG choose 1 person who is the Head (HoMTG)<br>the HoMTG must have the opprtunity to directly communicate with a <br>spokesperson of the developerteam who is responsible for that module (MSP),
<br>that modulespokeperson(MSP) can handle the certain tickets in trac and <br>can coordinate what testing the moduletesters need to do by associating <br>open tickets to the specific moduletestergroup(MTG). Is this possible
<br>within Trac?.<br> The "MTG Email" for example gets a few tickets from its MSP where he <br>decided they are important to get tested right now.<br>When the testing is done each tester within that group reports positive
<br>or negative results to the MSP.<br><br>So far , so good.<br>At this point the question is: in which form should an effective TEST <br>RESULT REPORTING happen. It does not make sense if everybody reports in <br>a different way, we have to have a certain plan or a certain form (
<br>where do i put the used OS, the used browser, the error message, the <br>line or row, the filename etc. )that we can follow and write down the <br>results without worrying about if the MSP can read and understand the
<br>reported results. The MSP must be able to read the report witrhin a <br>minute to tie in with his solution or ongoing tests. So i think <br>something like a testing report solution should be available to the <br>MTGīs that is similar in every MTG.
<br>By having this, it is much easier for non- developers like me or Kim or <br>the big user community, who can still provide extensive testing and are <br>interested in more than just using vTiger, to report bugs, as in trac
<br>one might be a little lost. But maybe at this point i just donīt really <br>understand TRAC. Than i excuse and maybe someone who is deeply into trac <br>can think this procedure to an end? Maybe the above described MTG/ MSP
<br>thing is already possible and i just donīt know?<br><br>Well, however you think it could be organized, i would love to be part <br>of a MTG for any part in vTiger and i would of course help in organising <br>these MTG groups if you like.
<br><br>Greetings<br>Torsten<br><br>shankar schrieb:<br> </pre>
<blockquote type="cite">
<pre>Fair enough.<br>Let us have groups that specialize in testing modules.<br><br>I would like to have volunteers who can ensure that specific modules <br>are well-tested. Kindly discuss among yourself and nominate the
<br>QA-head for that module. Any one who is thorough well-known in this <br>mailing list and the community could come forward and co-ordinate <br>this, well, that would be preferable but I leave that to the mailing <br>list decision.
<br><br>*Richie*<br><br><br>Kim Haverblad wrote:<br> </pre>
<blockquote type="cite">
<pre>Good idea about testing teams that have a protocoll of test that is<br>needed to been and so on. This gives also more community users the<br>possibility of giving a helping hand - not all of us are developers :-)
<br><br>/Kim<br><br>Torsten Zenk skrev:<br> <br> </pre>
<blockquote type="cite">
<pre>Hello,<br>i understand that you see 150 bugs fixed, what is a great amount in that <br>short period of time, and see that the last release announcement was for <br>mid of Jan 2007, but i made the experience that people donīt want to
<br>deal with bugs and at the moment they are not so satisfied with 5.02, so <br>>from that view i would tend to ask for release.<br>On the other side, if you wait 4 weeks more or longer and then have a <br>bugfree RC that is then really tested intensivly by the willing
<br>community on different OSīs to find out if the setup and everything <br>works allright, i would tend to say thatīs the better way and go for a <br>5.0.3 final.<br><br>Maybe we could build up testing teams that particularly test one small
<br>part of vtiger when the core team thinks that a certain part is really <br>working bugfree, for instance just the mail section, just the invoices <br>oder just the organisations and each team concentrates on that and just
<br>handles the bugs that trac holds for that particular part?<br>Just some thoughts<br><br>Best Regards<br>Torsten Zenk<br>_______________________________________________<br>Reach hundreds of potential candidates - <a href="http://jobs.vtiger.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://jobs.vtiger.com</a> <br> <br> </pre>
</blockquote>
<pre> <br> </pre>
</blockquote>
</blockquote>
<pre>_______________________________________________<br>Reach hundreds of potential candidates - <a href="http://jobs.vtiger.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://jobs.vtiger.com
</a> <br><br> </pre>
</blockquote>
<br>
</span></div></div>
<br>_______________________________________________<br>Reach hundreds of potential candidates - <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://jobs.vtiger.com" target="_blank">http://jobs.vtiger.com
</a><br><br></blockquote></div><br>