33
edits
Changes
Jump to navigation
Jump to search
Line 30:
Line 30: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Summer of Code/2014/Activity Unit Tests (view source)
Revision as of 16:51, 17 March 2014
, 16:51, 17 March 2014no edit summary
* What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
* What is the timeline for development of your project? The Summer of Code work period is from May 19 - August 22; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (27 June); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
<br>
{| class="wikitable"
|-
! Week / Days !! Work to be Done
|-
| Pre - 5th May || Talk to the mentors about the framework we are going to follow. This would include how the tests would be structured, what will be the key elements to target.
|-
| 6th May - 20th May || Get the initial testing done on HelloWorld. Show samples to mentors and decide on a framework.
|-
| 20th May - 27th May - (Week 1) || Start writing tests for Read / Write
|-
| 28th May - 3rd June - (Week 2) || Tests for Log & Terminal.
|-
| 3rd June - 10th June - (Week 3) || Tests for Calculate & Chat.
|-
| 10th June - 17th June - (Week 4) || Tests for Image & ImageViewer.
|-
| 17th June - 24th June - (Week 5) || Tests for Browse and start working on the initial tests for TurtleArt
|-
| 24th June - 1st July - (Week 6) || Mid-Term Evaluations - '''Buffer Week'''
|-
| 1st July - 8th July - (Week 7) || Tests for TaBasic, TaBlock, TaCanvas
|-
| 8th July - 15th July - (Week 8) || Tests for TaExportLogo, TaExportPython, TaLogo
|-
| 15th July - 22nd July - (Week 9) || Finish up Turtle Art and Start working on Pippy
|-
| 22nd July - 29th July - (Week 10) || Buffer
|-
| 29th July - 5th August - (Week 11) || Tests for Pippy
|-
| 5th August - 12th August - (Week 12) || Tests for Pippy and Start writing guide on testing on the wiki
|-
| 12th August - 19th August - (Week 13) || More review, some final touches, some final fixing of glitches
|-
| 19th August - 26th August - (Week 14) || Firm Pencil Down & Final Evaluations
|}
* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.
* Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.