Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
swat:design [2007/10/15 11:52] isuru |
swat:design [2009/07/06 20:36] (current) |
||
---|---|---|---|
Line 9: | Line 9: | ||
__Objectives__ | __Objectives__ | ||
- | The major objective of this process is to improve the quality of the code available in the repository ensuring all the conventions are met as in the following url. http:// | + | The major objective of this process is to improve the quality of the code available in the repository ensuring all the conventions are met as in the following url. http:// |
__Team__ | __Team__ | ||
Line 15: | Line 15: | ||
- mahesh [at] opensource [dot] lk | - mahesh [at] opensource [dot] lk | ||
- viraj [at] gmail [dot] com | - viraj [at] gmail [dot] com | ||
+ | |||
+ | __Modules under SWAT for this week__ | ||
+ | - **Organization Registry** | ||
+ | - **Request Management System** | ||
+ | - Inventory Management System | ||
+ | - Catalog System | ||
+ | |||
+ | |||
+ | |||
Line 22: | Line 31: | ||
=====Main | =====Main | ||
- | *Assigned modules per week will be validated against the PHP coding conventions available at http:// | + | *Assigned modules per week will be validated against the PHP coding conventions available at http:// |
- | | + | |
| | ||
- | **Following tests will be done using PHPCheckstyle** | + | **Following tests will be done using PHPCheckstyle(http:// |
* Test " | * Test " | ||
Line 46: | Line 55: | ||
function definition and the default value of " | function definition and the default value of " | ||
- | | + | |
+ | **The other convention validations will be done manually** | ||
- | == PHPCheckstyle | + | __PHPCheckstyle |
* Download phpcheckstyle from http:// | * Download phpcheckstyle from http:// | ||
Line 55: | Line 65: | ||
* Unzip the content to a folder i.e: | * Unzip the content to a folder i.e: | ||
- | * Uncomment | + | * Comment |
<test name=" | <test name=" | ||
Line 70: | Line 80: | ||
| | ||
+ | __Steps to validate a file against the convention__ | ||
+ | - Parse the file using PHPCheckstyle and generate the violation report | ||
+ | - Identify the common coding convention violations in the file manually | ||
+ | - Submit a bug in the bug tracker attaching the violation report and the manually identified violations | ||
+ | - For each and every file of a module this process should be repeated | ||
+ | - Developers are also expected to use PHPCheckstyle and validate their code before they mark the bug ' | ||
Line 75: | Line 91: | ||
- | ===== Module developer conventions | + | |
+ | |||
+ | |||
+ | ===== Module developer/ | ||
| | ||
+ | Developer must use the existing reusable libraries.i.e paging, | ||
| | ||
+ | In each and every module ' | ||
*File structure | *File structure | ||
+ | Under inst folder mysql-dbcreate.sql, | ||
| | ||
- | + | All the requests to the server should be navigated according to the front controller design pattern | |
+ | |||
+ | |||
+ | |||
+ | |||
===== Integration testing ===== | ===== Integration testing ===== | ||
| | ||
+ | Request Management System, | ||
+ | |||
+ | __Major Integration issues__ | ||
+ | |||
+ | * Integrate the Request Management System with the security framework | ||
+ | Any user should | ||
+ | |||
+ | *All the requests and pledges should be coupled with the inventory management system | ||
+ | |||
+ | |||
+ | |||
| | ||