This page contains my experience in GSoC 2011 with org MoinMoin. It has ToDo's, Discussions, Amendments etc both by me, and by my mentors. It'll act as reference before and after 23rd May.
Repo Link: Testing_Project_Repo
Project Updates On:
TODO
https://bitbucket.org/89hardy/pytest_moin/changeset/e18eb0e986ab
Please fix that ASAP. IIRC, we talked about that, why didn't you fix it?
Plan
Community bonding period:
- Get a clear picture of the current bugs related to tests.
- Read the documentations of py.test 2.0, unit tests and mercurial.
- Read and Run every test individually and compare tests written on version 1.3.4 to version 2.0.3 to track related bugs.
- Talk to mentors and draw up a detailed roadmap of the entire project.
June 8 - June 13 (Quarter-Term)
- Complete log of the current bugs.
- Sanity checks of the tests which need not be re-written.
- Tests which cannot run because of minor conditions like missing external libraries will be fixed.
- Porting of tests from py.test 1.3.4 to pytest 2.0.3.
- Fixing bugs noticed after porting is completed.
June 14 - July 11 (Mid-Term)
- Compatibility of all the tests to py.test 2.0.3 will be ensured.
- All tests with minor glitches and which require normal sanity check will now be working.
- Test coverage will be reviewed and improvement of state of tests will be done.
July 12 - Aug 1 (Three-Quarter-Term)
- Re-write all the tests and make them 'good tests' keeping minimum memory usage in mind.
- Review all tests and correct the broken code, if any. 3.Adding the remaining tests in the package and keep a check on reviews.
Pencil Down Date (Aug 22)
- At this point, the entire test package will be working correctly using minimum RAM possible. Carrying on successful tests will now be possible.
- Regular update regarding the progress of the project will be done on blog throughout the project.
- A detailed documentation will now be available for other open source enthusiasts.