thepeach / mag Goto Github PK

also, being able to automate everything would be great, but in the meantime just being able to run the tests via phpunit would be absolutely awesome.

Current error is:
mag $ phpunit --configuration protected/tests/phpunit.xml .
PHPUnit 3.5.0 by Sebastian Bergmann.

EEEEEE

Time: 0 seconds, Memory: 8.50Mb

There were 6 errors:

1) SiteTest::testIndex
PHPUnit_Framework_Exception: Could not connect to the Selenium RC server.

/home/peach/public_html/yii-1.1.6.r2877/framework/test/CWebTestCase.php:61

2) SiteTest::testContact
PHPUnit_Framework_Exception: Could not connect to the Selenium RC server.

/home/peach/public_html/yii-1.1.6.r2877/framework/test/CWebTestCase.php:61

3) SiteTest::testLoginLogout
PHPUnit_Framework_Exception: Could not connect to the Selenium RC server.

/home/peach/public_html/yii-1.1.6.r2877/framework/test/CWebTestCase.php:61

4) SiteTest::testIndex
PHPUnit_Framework_Exception: Could not connect to the Selenium RC server.

/home/peach/public_html/yii-1.1.6.r2877/framework/test/CWebTestCase.php:61

5) SiteTest::testContact
PHPUnit_Framework_Exception: Could not connect to the Selenium RC server.

/home/peach/public_html/yii-1.1.6.r2877/framework/test/CWebTestCase.php:61

6) SiteTest::testLoginLogout
PHPUnit_Framework_Exception: Could not connect to the Selenium RC server.

/home/peach/public_html/yii-1.1.6.r2877/framework/test/CWebTestCase.php:61

FAILURES!
Tests: 6, Assertions: 0, Errors: 6.

Scrap mootools dependancy and update JQuery to latest version.
Define correctly the application architecture and mockup the interface (or review the past mockups if any could be found)

As long as a decision is made, all checks should be done and properly tested across all platform.

functionality should be given by:

• login
• logout
• register
• email verification (see #11)

Start moving over Yii for the server side implementation

The whole site should support different graphical styles one per each gallery

after transitioning under Yii it's needed a little bit of rearranging of the directories previously laid down.
the original situation was:

• gallery/
• images/
• includes/
• settings/
• index.html

now everything should move inside the proper directories structure provided by Yii

As it is right now there's no server side application.
As long as an API is needed for the client side application to work something along the lines of a server-side application could really help.

Starting ideas:

• have Yii as underlying framework
• use as less resources as possible
• do not use mysql (at least for the beginning), start with xml would be nice, making the transition less problematic and being able to deal with multidimensional data structures without getting mad with references and such things.

What has to be done (tickets needs to be opened for it)

• sketch out a protocol/API to be exposed the client side should be able to work with (bandwidth should be kept in mind) (see #7 and #8)
• given the previous point, have Yii work with xml datastructures instead of databases and have models work without too much hassle.
• if the first point is not feasible, then consider other opportunities as Yii should work with berkdb or whatever is called now
• the API could provide a multi protocol output (json/rdf/etc)

The main data sources are:

• users
• media contents (images, videos, music, flash?)

This schema should be then used to define the protocol used by the client-side application.

Basic form for user registration shouldn't require double password enter, but only email verification.
Email is hence considered unique in the whole db.

In order to have a as fast as possible application using as less resources by any given time is a must, the application should rely on that

Communication protocol is in turn used by the API
Define what is needed and when, modularize everything and define API interface with the data structure that has to be returned.

DONE? when the data protocol is defined with all entry points defined by the APIs