A simple (but meeting the minimum requirements) shop system will be implemented. Using 1-click functionality (no basket) and using Click & Buy and paypal as means of payment. Additional data for the purchasing process will be collected here. There are packages which could be purchased. The packages to be purchased are displayed in a block. When buying process is completed a hook function must be called with the item bought. The shop must be integrated in an existing theme that will be provided to the coder.
A1) Complete and precise implementation of the description of the bid request.
A2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
A3) Buyer will receive exclusive and complete copyrights to all work purchased. Third party software may be included as long as they are published under a license compatible with the GNU GPL.
A4) Software must be platform, browser and os independent.
A5) Software must be provided with a mercurial repository initialized when the work started (typically by unarchiving the sources and running hg init + hg commit at the toplevel)
A6) The work must be commited under mercurial on a daily basis.
A7) The reason for each change (not the change itself) must be explained in the ChangeLog file at the root the package tree.
A8) The software must be delivered in source form exclusively and it must be possible to create the binary form with a single command line.
R1) A set of unit tests covering 100% of the code written or modified for the job. There is no need to cover the code that already existed and that was not modified.
R3) Implement a verbose mode for running the tests so identifying which unit test fails and why is straightforward.
R5) The tests must be implemented using the same techniques as the pre-existing tests of the software being modified. It is not acceptable to create a new test environment. S1) Complete and precise implementation of the description of the bid request.
S2) Complete and fully-functional working web site(s) with no absolute URL in it.
SP1) The tests can be run individually (in addition to all at once) using either a URL permalink or a command line option. Each functionality described in the specifications must be associated with a permanlink and/or option.
SP2) The specifications must be modified to add a link to the test(s) that demonstrate its implementation.