Re: [Dolibarr-dev] about project : Improved code coverage

[ray]



Hi,

 

why does none care about the Automatic testing process?

 

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:

Dolistore.com and Dolibarr.fr are moved to a new server

http://www.dolibarr.org/component/content/article/1-announces/139-dolistorecom-and-dolibarrfr-down

 

 

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

To: raygsoc2013; Posts about Dolibarr ERP & CRM development and coding

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,

 

Marcos García

address@hidden

2013/3/22 ray <address@hidden>

Hi all,

 

I am Ray. I am reading more the idea: Improved code coverage . 

About the topic, at least two things should be done:

1.  create more test cases to increase the code-coverage of the test-suite 

https://github.com/raygsoc2013/dolibarr/tree/develop/test

2.  set up the necessary scripts to automate this.

https://github.com/raygsoc2013/dolibarr/tree/develop/scripts

 

there are more thing I want your guys' help at this time to help me dig into Dolibarr deeply.

1.  does Dolibarr has a CI env. (Jenkin build?)

2.  does Doliarr has a code coverage page to let me know which code is covered and which code is not covered?

 

 

I have fork the project my selves:  https://github.com/raygsoc2013/dolibarr/tree/develop/test 

I am very familiar with the CI env and PHP code coverage, because I just finished a similiar project when I Intern on Yahoo! last year.  

1. PHP UNIT code and Functional testing code.

2. Commit to GIT will trigger a CI build.

3. The CI build is done by: slenium + Firefox+ Xvfb (so that we dont need display)

4. output the code coverage report.

 

I would like to send some patch to improve the code coverage. I am looking forward to hearing from you. thanks

 

 

 

---

ray

 

From: ray

Date: 2013-03-19 16:34

To: dolibarr-dev; Laurent Destailleur (eldy)

Subject: Re: Re: [Dolibarr-dev] I am Ray, I am glad to join Dolibarr gsoc

Thanks eldy,

 

But I think I must start earlier and make a better preparation about my application of GSOC.

 

With this aim, I have took some steps:

1. Read the developer guide on http://wiki.dolibarr.org/index.php/Developer_documentation

2. I spent some time on reading the API, which will be a

great help to dig into code. http://www.dolibarr.org/html_doxygen/db/d22/class_account.html 

3.  Follow some test document on Dolibarr http://wiki.dolibarr.org/index.php/Main_Page#Testers_documentation 

4.  Doing some pratice on PHPUnit and PHP code coverage.

 

 

Are there more thing that I need to do before the application? This is

my first time to join GSOC, so I am not quite sure about it. can

you give me some tips and help, many thanks!

 

---

ray

 

From: Laurent Destailleur (eldy)

Date: 2013-03-19 16:26

To: dolibarr-dev

Subject: Re: [Dolibarr-dev] I am Ray, I am glad to join Dolibarr gsoc

Mentors are not yet defined because we must first wait that google accept us as a mentor.
We must wait the 8th of april for that.

Le 19/03/2013 04:49, ray a écrit :

HI,

 

Can someone share with me who will be the mentor about the topic: Idea 5 : Improved code coverage

I would like to contact with him deeper. thanks

 

 

Following is some of my info:

 

I am Ray, I am glad to join Dolibarr. Following are some information about Me.

1. I am a student from Academy of Science, China, major at Computer

science. this year is my third-year on university.

2. I am good at PHP programming, and I love open source.

 

 

 I would like to join Dolibarr project on Google Summer of Code. I read some idea listed on http://wiki.dolibarr.org/index.php/Google_Summer_of_Code_Ideas_2013 .  I am quite interested on the idea:  Idea 5 : Improved code coverage

 

 

With this aim, I have took some steps:

1. Read the developer guide on http://wiki.dolibarr.org/index.php/Developer_documentation

2. I spent some time on reading the API, which will be a

great help to dig into code. http://www.dolibarr.org/html_doxygen/db/d22/class_account.html 

3.  Follow some test document on Dolibarr http://wiki.dolibarr.org/index.php/Main_Page#Testers_documentation 

4.  Doing some pratice on PHPUnit and PHP code coverage.

 

 

Are there more thing that I need to do before the application? This is

my first time to join GSOC, so I am not quite sure about it. can

someone give me some tips and help, many thanks!

 

 

 

---

ray

 

From: ray

Date: 2013-03-18 23:06

To: dolibarr-dev

Subject: I am Ray, I am glad to join Dolibarr gsoc

Hello everyone,

 

I am Ray, I am glad to join Dolibarr. Following are some information about Me.

1. I am a student from Academy of Science, China, major at Computer

science. this year is my third-year on university.

2. I am good at PHP programming, and I love open source.

 

 

 I would like to join Dolibarr project on Google Summer of Code. I read some idea listed on http://wiki.dolibarr.org/index.php/Google_Summer_of_Code_Ideas_2013 .  I am quite interested on the idea:  Idea 5 : Improved code coverage

 

 

With this aim, I have took some steps:

1. Read the developer guide on http://wiki.dolibarr.org/index.php/Developer_documentation

2. I spent some time on reading the API, which will be a

great help to dig into code. http://www.dolibarr.org/html_doxygen/db/d22/class_account.html 

3.  Follow some test document on Dolibarr http://wiki.dolibarr.org/index.php/Main_Page#Testers_documentation 

4.  Doing some pratice on PHPUnit and PHP code coverage.

 

 

Are there more thing that I need to do before the application? This is

my first time to join GSOC, so I am not quite sure about it. can

someone give me some tips and help, many thanks!

 

 

---

ray

_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev

-- 
Eldy (Laurent Destailleur).

EMail: address@hidden
Web: http://www.destailleur.fr

Dolibarr (Project leader): http://www.dolibarr.org
To make a donation for Dolibarr project via Paypal: address@hidden
AWStats (Author) : http://awstats.sourceforge.net
To make a donation for AWStats project via Paypal: address@hidden
AWBot (Author) : http://awbot.sourceforge.net
CVSChangeLogBuilder (Author) : http://cvschangelogb.sourceforge.net

_______________________________________________
Dolibarr-dev mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/dolibarr-dev