I was planning to fix Issue668 as my fourth release.
After talk to professor about this issue, I quickly put the right code back.
However, becuase the branch I was working on did not merge into the master branch on mozilla/brackats until the last minute, it force me to change my plan.
I would like to keep working on that issue (not for acdamic study actually make me feel better).
Luckly, I find another thing for myself to do.
Several days ago, I create a Starting Kit for thible. (see Blog)
It takes a lot effort to understand the background logic.
However, what take most of the time is writting the tutorial page and the Teaching Kit..
In this case, I was wondering: why don't I make a tutorial for teaching people how to make a Starting Kit?
Then I worked on it.
I first modified the old Teaching Kits into a template.
Link: Template1 & Template2.
View:
&
These templates would save huge amout of time for people who want to ceate a new Staring Kit.
Then, I modified the tutorial.html.
By adding a little bit of text, a new tutorial would quickly be made by contributors.
Finally, I use the tempate of the tutorial.html to make a tutorial for creating new Starting Kit.
Views of both page:
I was thinking about making the tutorial into a README.md version.
I will keep contact on this issue with the community and figure out the best solution.
Link to the pull request: here
My new blog on DPS909 in Seneca College. I believe it would become a good start for me on Open Source Programming.
Saturday, 22 April 2017
Lab 8 - Unit Test
What is the best thing that a programmers could ever meet? PASS the test, No bug!
That is what I feel after I saw this page:
In this lab, we made our own test for our own program.
Try to broken my own program is a really strange feeling. (usually people won't positively look for trouble to themselves)
My program did broken several times during my test, and some times I have to spend an hour change the code & google for sulotion.
The test file is much longer that the original file.
Cover every different cases is not easy. I talked to my classmates about the possible cases that might broke my program.
Thank god, I pass they all. Testing other people's job is never a easy work.
That is what I feel after I saw this page:
In this lab, we made our own test for our own program.
Try to broken my own program is a really strange feeling. (usually people won't positively look for trouble to themselves)
My program did broken several times during my test, and some times I have to spend an hour change the code & google for sulotion.
The test file is much longer that the original file.
Cover every different cases is not easy. I talked to my classmates about the possible cases that might broke my program.
Thank god, I pass they all. Testing other people's job is never a easy work.
Releasse 3 - Fix few bugs about Starting Kit.
As I keep working for the Starting Kits, I find there are huge amout of bugs. (probably because no one really goes into those Kits)
Here are few bugs I found: Issue2012, Issue2028 and Issue2033.
I fixed every bug that I am able to fix (Pull2027), but most of the bugs are bugs that normal contributors cannot approached. (because Starting Kits are all works published on other people's accout).
I opend up issues, and hopefully that administrators of thimble would be able to fix those bugs.
Also, as people mentioned in the Issue1917, stay-calm project under the default folder is useless.
In this case, I removed all those files after test.
Testing this is not a easy job. Because the thimble reciently updated to bramble, I have to run both old/new code, in order to make sure that everything works fine.
Here is the work I did: Pull2011
Here are few bugs I found: Issue2012, Issue2028 and Issue2033.
I fixed every bug that I am able to fix (Pull2027), but most of the bugs are bugs that normal contributors cannot approached. (because Starting Kits are all works published on other people's accout).
I opend up issues, and hopefully that administrators of thimble would be able to fix those bugs.
Also, as people mentioned in the Issue1917, stay-calm project under the default folder is useless.
In this case, I removed all those files after test.
Testing this is not a easy job. Because the thimble reciently updated to bramble, I have to run both old/new code, in order to make sure that everything works fine.
Here is the work I did: Pull2011
Subscribe to:
Posts (Atom)