qa:testfest:webdev
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
qa:testfest:webdev [2008/03/28 03:08] – davidc | qa:testfest:webdev [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Test Fest Web development team and strategies | + | ====== PHP TestFest 2008 ====== |
+ | |||
+ | //This page contains out-dated material and is archived here for informational purposes. For recent information, | ||
+ | |||
+ | ===== Test Fest Web development team and strategies ===== | ||
The PHP Project is happy to announce the development of it's Test Fest Web Platform built on top of the Solar Framework. There has been quite a bit of thinking and meditation on the subject from my part (David) and I have came up with the solution to our problem. Solar. It is developed by our great open source contributor and colleague Paul M. Jones and is very robust but still very fast and flexible. | The PHP Project is happy to announce the development of it's Test Fest Web Platform built on top of the Solar Framework. There has been quite a bit of thinking and meditation on the subject from my part (David) and I have came up with the solution to our problem. Solar. It is developed by our great open source contributor and colleague Paul M. Jones and is very robust but still very fast and flexible. | ||
- | It has a rather small footprint and the learning curve is not as steep as some other frameworks. There can still be discussions of course if anyone has an objection | + | It has a rather small footprint and the learning curve is not as steep as some other frameworks. There can still be discussions of course if anyone has any objections |
+ | |||
+ | Another reason that made us choose Solar is that it's been around for a while now and has proven it's stability, and moreover, it's documentation is well written and simple/easy to understand. You can run the examples straight out of the box. | ||
I'd like to remind everyone that we are still looking for people to help us with the design of the web interface. | I'd like to remind everyone that we are still looking for people to help us with the design of the web interface. | ||
Anyways, here we go with the sections we'll need on that platform/ | Anyways, here we go with the sections we'll need on that platform/ | ||
+ | |||
Line 16: | Line 23: | ||
* Registration Area (As a simple user, or as a group) | * Registration Area (As a simple user, or as a group) | ||
* Login Area (Where the group/user will enter their user name and password) | * Login Area (Where the group/user will enter their user name and password) | ||
+ | * Live Test Writing Area: A place where contributors can write tests online ([[http:// | ||
* File upload area (A contributor will be able to upload single .phpt file or .zip/ | * File upload area (A contributor will be able to upload single .phpt file or .zip/ | ||
* Files Area (A place where the contributor will see all his submitted tests (Uploaded, Confirmed, In Review, Accepted, Refused etc) | * Files Area (A place where the contributor will see all his submitted tests (Uploaded, Confirmed, In Review, Accepted, Refused etc) | ||
Line 21: | Line 29: | ||
* Confirmed: The contributor knows the patch is ready to be reviewed and cannot change it. | * Confirmed: The contributor knows the patch is ready to be reviewed and cannot change it. | ||
* In Review: This file is currently being reviewed by one of the mentors | * In Review: This file is currently being reviewed by one of the mentors | ||
- | * Accepted: This test has been accepted and is going to be committed. | + | * Accepted: This test has been accepted and has been committed. A diff will be displayed between the submitted and the committed |
* Refused: This means the test has been refused (A reason will be supplied upon refusal) | * Refused: This means the test has been refused (A reason will be supplied upon refusal) | ||
* His Files area will also have the ability to view the file online, and the ability to delete it. | * His Files area will also have the ability to view the file online, and the ability to delete it. | ||
+ | | ||
==== Mentors Area ==== | ==== Mentors Area ==== | ||
Line 31: | Line 40: | ||
* Login Area: Where the mentor logs in | * Login Area: Where the mentor logs in | ||
* Test Review area: A place where the mentor can see all the " | * Test Review area: A place where the mentor can see all the " | ||
- | * Announcement Area: A place for the mentors to announce news on the main page of the Test Fest | + | * Announcement Area: A place for the mentors to announce news on the main page of the Test Fest (low priority) |
+ | * Live Test Test Area: A place for the mentors to Test the patch directly online. (@TODO) (low priority) | ||
==== General process & evolution Area ==== | ==== General process & evolution Area ==== | ||
- | This whole section will behave a bit like a blog for the Test Fest. All mentors will be able to post their news (If they have any) and all the accepted/ | + | This whole section will behave a bit like a blog for the Test Fest. All mentors will be able to post their news (If they have any) and all the accepted/ |
- | Nothing too fancy, something simple, clear, easy to follow. | + | ==== Committing Submissions and Cronjob ==== |
- | Perhaps | + | Mentors that commit tests that are even partially derived by a submission should note down the URL's to the submission that helped |
qa/testfest/webdev.1206673697.txt.gz · Last modified: 2017/09/22 13:28 (external edit)