GSOC2013_PMA_Automated Testing: 2013

In the firstly week, (0602-0608)

I have finished:
1. submited the needed materials to Google
2. Warm up on PMA code
3. communicate with Mentor (Michal) about the task split.

Doing now:
I will focus on the first part of code:
- DBI (libraries/dbi)

Hope to have a good result this week!

Adam

Job Split

the final work split:
===================Adam ==================

- Schema designer (libraries/schema)

- Import (libraries/plugins/import)

- Transformations (libraries/plugins/transformations)

- DBI (libraries/dbi)

- Relations (libraries/relation*)

- SQL parser/analyzer (libraries/sqlparser, libraries/parse*)

- IP allow/deny rules (libraries/ip_allow*)

- Table operations (libraries/Table*)

===================Ayush==================

- Plugin system (libraries/plugins/Plugin*, libraries/properties/*)

- Export (libraries/plugins/export)

- Authentication (libraries/plugins/auth)

- Setup script + user configuration (libraries/config, setup,

libraries/user_pref*)

- Tracker (libraries/Tracker)

- String manipulations (libraries/string*)

- Charset conversions (libraries/char*, libraries/iconv*,

libraries/kanji*)

2013年5月30日星期四

About the Job split

In my opinion:

the files in Library Folder can be splited to:

1. Display logic: the php files in libraries folder

this is a large part of code.

config (2.03%)

dbi (3.01%)

engines (91.55%)

gis (70.24%)

navigation (24.70%)

schema (0.00%)

properties (0.00%)

rte (47.12%)

3. Files should be removed from code coverage report

phpseclib

plugins

===============================

I would like to take:

1. Display logic: the php files in libraries folder

2. config (2.03%)

3. navigation (24.70%)

2013年5月29日星期三

the code coverage on PMA

from the code coverage link: http://ci.phpmyadmin.net/job/phpMyAdmin/cloverphp/?

we should discussion every folder. some folders are unneeded to contain on code coverage.

First week_Application

In this blog, I try to mark something I did while I apply for PMA.

1. I prepared some patches:

refer to : https://github.com/phpmyadmin/phpmyadmin/commits?author=adamgsoc2013

2. following is the proposal I wrote:

https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/adam_kang/1

3. discussion with Mentors

thanks for all mentors from PMA.

Marc https://github.com/lem9

Michal https://github.com/nijel

Dieter

2013年5月28日星期二

Starting Now, my GSOC2013

Hi all,
I am Adam Kang. this blog is to track my GSOC2013 with PhpmyAdmin. (http://www.phpmyadmin.net/)
https://google-melange.appspot.com/gsoc/proposal/review/google/gsoc2013/adam_kang/1

PMA is a popular web based database management tool. It usually undergoes new releases, bug fixes, new feature development and refactoring. Since the PMA production code is changed frequently and our code is finished by developers from all over the world, in order to guarantee the production quality, it is very necessary to run Unit testing on Jenkins (Hudson). Unit Tests have several benefits to us. It allows us changing code quickly under full testing. By running unit tests, a developer can identify whether his latest changes to the code base has broken anything. Unit Tests can also help new developers really understand the design of the code and it can give our developers visual feedback about which lines are covered. From PMA CI Page, Currently, the code coverage of PMA is 18.3%. More code coverage means more guarantee to production.
Goal:
1. Increase the code coverage to a reasonable percentage (80%)
2. Set up the necessary scripts to automate unit testing.
3. Help other developers to set up their unit test cases.
4. Functional test case to cover render issue

Strategy: we should cover core code to a high level (90%) at firstly and then spent some time on the other stuff.

Hope to have a great code summer with PMA.

订阅：博文 (Atom)