[Vtigercrm-developers] should all the blocker and critical be fixed for the 5.0.3 ?

[clement chazarra]

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.

Regards,
Clem

On 1/24/07, richie <richie at vtiger.com> wrote:
>
>  Guys, you have to help me figure this out.
> What about the other sages out there. Any ideas please?
>
> 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.
>
> 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.
> Let me know please.
>
> Fathi, could you tell how we can add custom fields to the trac please?
>
> *Richie*
>
> Torsten Zenk wrote:
>
> Hi Richie,
> maybe i can point out how i think it could work very smoothly:
>
> If a group of moduletesters (MTG) has 2- 3 Testers (1 on each plattform
> should be perfect), those 3 communicate via email or maybe even in a
> Testingforum if you could centrally set one up.
> The MTG choose 1 person who is the Head (HoMTG)
> the HoMTG must have the opprtunity to directly communicate with a
> spokesperson of the developerteam who is responsible for that module (MSP),
> that  modulespokeperson(MSP) can handle the certain tickets in trac and
> can coordinate what testing the moduletesters need to do by associating
> open tickets to the specific moduletestergroup(MTG). Is this possible
> within Trac?.
>  The "MTG Email" for example gets a few tickets from its MSP where he
> decided they are important to get tested right now.
> When the testing is done each tester within that group reports positive
> or negative results to the MSP.
>
> So far , so good.
> At this point the question is: in which form should an effective TEST
> RESULT REPORTING happen. It does not make sense if everybody reports in
> a different way, we have to have a certain plan or a certain form (
> where do i put the used OS, the used browser, the error message, the
> line or row, the filename etc. )that we can follow and write down the
> results without worrying about if the MSP can read and understand the
> reported results. The MSP must be able to read the report witrhin a
> minute to tie in with his solution or ongoing tests. So i think
> something like a testing report solution should be available to the
> MTG´s that is similar in every MTG.
> By having this, it is much easier for non- developers like me or Kim or
> the big user community, who can still provide extensive testing and are
> interested in more than just using vTiger, to report bugs, as in trac
> one might be a little lost. But maybe at this point i just don´t really
> understand TRAC. Than i excuse and maybe someone who is deeply into trac
> can think this procedure to an end? Maybe the above described MTG/ MSP
> thing is already possible and i just don´t know?
>
> Well, however you think it could be organized, i would love to be part
> of a MTG for any part in vTiger and i would of course help in organising
> these MTG groups if you like.
>
> Greetings
> Torsten
>
> shankar schrieb:
>
>  Fair enough.
> Let us have groups that specialize in testing modules.
>
> I would like to have volunteers who can ensure that specific modules
> are well-tested. Kindly discuss among yourself and nominate the
> QA-head for that module. Any one who is thorough well-known in this
> mailing list and the community could come forward and co-ordinate
> this, well, that would be preferable but I leave that to the mailing
> list decision.
>
> *Richie*
>
>
> Kim Haverblad wrote:
>
>  Good idea about testing teams that have a protocoll of test that is
> needed to been and so on. This gives also more community users the
> possibility of giving a helping hand - not all of us are developers :-)
>
> /Kim
>
> Torsten Zenk skrev:
>
>        Hello,
> i understand that you see 150 bugs fixed, what is a great amount in that
> short period of time, and see that the last release announcement was for
> mid of Jan 2007, but i made the experience that people don´t want to
> deal with bugs and at the moment they are not so satisfied with 5.02, so
> >from that view i would tend to ask for release.
> On the other side, if you wait 4 weeks more or longer and then have a
> bugfree RC that is then really tested intensivly by the willing
> community on different OS´s to find out if the setup and everything
> works allright, i would tend to say that´s the better way and go for a
> 5.0.3 final.
>
> Maybe we could build up testing teams that particularly test one small
> part of vtiger when the core team thinks that a certain part is really
> working bugfree, for instance just the mail section, just the invoices
> oder just the organisations and each team concentrates on that and just
> handles the bugs that trac holds for that particular part?
> Just some thoughts
>
> Best Regards
> Torsten Zenk
> _______________________________________________
> Reach hundreds of potential candidates - http://jobs.vtiger.com
>
>
>        _______________________________________________
> Reach hundreds of potential candidates - http://jobs.vtiger.com
>
>
>
> _______________________________________________
> Reach hundreds of potential candidates - http://jobs.vtiger.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20070124/20489993/attachment-0004.html