|
From: | ray |
Subject: | Re: [Dolibarr-dev] [Pull request] Improved code coverage |
Date: | Sun, 7 Apr 2013 23:48:01 +0800 |
Hi,
I sent a pull request about UNIT testing, can someone help me to have a
review? thanks
ray
From: ray
Date: 2013-04-07 22:36
To: dolibarr-dev
Subject: Re: Re: [Dolibarr-dev] about project : Improved code
coverage Hi,
why does none care about the Automatic testing process? I think
Automatic testing process is very important to production qualitity.
I think more about the process. I think we need functional case as well.
In my mind, the regression tests is different from the unit tests. or in
other word, we can say that the regression test include Unit tests. the
regression test can include function test case beside unit tests.
In order to gurantee the code quality, UNIT test just cover the code logic,
but Fuinctional test can be end to end case with real case.
Benefits: 1. check the page is loaded correctly
2. check the page is working well on
GradeA browsers.
3. check the css/js is working well ==========my previous mail but no reply=====
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 17:01
To: eldy10; dolibarr-dev
CC: marcosgdf
Subject: Re: Re: [Dolibarr-dev] about project : Improved code
coverage 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] |