|
From: | ray |
Subject: | Re: [Dolibarr-dev] about project : Improved code coverage |
Date: | Fri, 29 Mar 2013 17:01:58 +0800 |
Hi,
I have a question about current Automatic testing process.
When one guy finished a piece of code
Should he follows some instructions before check in code besides
Code-review?
1. UT implementation
2. Regression --> this will be checked by CI Job
3. running regression and UT on his dev box?
In my mind, the fomal processes should be:
1. add logic code
2. add UT code
3. test on dev box
4. run UT & regression test on dev box
5. code review after pass 1-4
6. checkin code
7. check CI build
.....
thanks ray
From: ray
Date: 2013-03-29 16:45
To: eldy10; dolibarr-dev
CC: marcosgdf
Subject: Re: Re: [Dolibarr-dev] about project : Improved code
coverage Hi,
from the link:
It said that Migration
finished on tuesday 29 2013.
How about the process now? I would like to cover the
code coverage project. so I am interested on the new CI env.
thanks
thanks
ray
From: Marcos
García
Date: 2013-03-22 20:06
CC: eldy10
Subject: Re: [Dolibarr-dev] about project : Improved code
coverage Hi Ray,
First, I'd like to tell you that every Dolibarr developer or contributor is
(or should be) subscribed to dolibar-dev list at nongnu.org, so you don't need to email us
directly.
Regarding your questions 1 and 2, Dolibarr has it's own project manager at
doliforge.org (https://doliforge.org/projects/dolibarr/).
There was a Jenkins CI environment but it seems that the link has disappeared. I
see Eldy posted an announcement in dolibarr.org (http://www.dolibarr.org/component/content/article/1-announces/139-dolistorecom-and-dolibarrfr-down)
telling that he is working with the migration of doliforge.org, maybe that's the reason why we
are not able to access Jenkins from doliforge...
Anyway, I think Eldy should tell us why it is not available right
now...
Regards, 2013/3/22 ray <address@hidden>
|
[Prev in Thread] | Current Thread | [Next in Thread] |