Ok, so I'm going to go back to my initial project plan and re assess things.
project wiki: containing basic information of the overall project. I will be updating it more frequently throughout 0.2 and 0.3.
Changes
- 0.1: Bug #226
While researching my first initial processing.js bug, I noticed when there was a comment // inside a character string, the parser would be happy to remove it, which is only the beginning. If there is ANYTHING inside a string that resembled code or keywords, it would break. the parser would grab the keyword, and change it to javasctipt. For example:
text("int i = 0;", 0, 15);
would then be parsed to:
text("var i = 0;", 0, 15);
After noticing this, I went right to the bug tracking system and found this. The bug I, myself just found. So, I'm going to complete that for my 0.1. I will also implement automated test cases for it. - 0.2: Bugs #133 and #230.
These have been bumped to 0.2 from 0.1. I will also do automated test cases for these too. - 0.3: TBD.
I hope with the experience I have gained, I can do three bugs, and implement automated test cases for them as well.
Conclusion
I've got down the process involved in doing this, and I hope to start back on 0.2 as soon as possible, Monday at the latest. It's best to start small, and start early. This stuff is not something that, for me, can always be accomplished in one night.
Hi Scott,
ReplyDeleteI finally found time to catch up with your blog, and I missed a lot! Which means that you are consistent with your work, and that's inspiring.
Anyway, I wanted to ask you what is an automated test case?
http://vocamus.net/dave/?p=1001
ReplyDeleteand mentioned in that post:
https://processing-js.lighthouseapp.com/projects/41284/writing-automated-tests
To sum it up, it's a serious of tests you run against your program, and is used when changes to a program are made, to make sure you didn't break any of the previous code. In this case, I added new code that I didn't want to be broken later, so I made a series of test cases to make sure it stays in tact. Helpful when you program a large program on your own, necessary when a large group of people program an even larger program.