Add meeting notes with Leo to the wiki page.
diff --git a/GSoC2011MelangeTesting.wiki b/GSoC2011MelangeTesting.wiki index 33c6866..a024557 100644 --- a/GSoC2011MelangeTesting.wiki +++ b/GSoC2011MelangeTesting.wiki
@@ -32,9 +32,11 @@ == Wednesday May 24, 2011 == ===Notes=== - Location: Gmail Chat - Chaired by: Leo (Chong Liu) - Notes taken by: Praveen + Location: Gmail Chat + + Chaired by: Leo + + Notes by: Praveen * Told Leo that I am going slow at the project and had not implemented the view yet that we were supposed to do. * We discussed what should the basic approach be while writing a test. @@ -44,6 +46,84 @@ ===Coding Plan for this week=== * Implement the view * Write test for at least one module in app.soc.logic + +== Friday May 27, 2011 == + +===Notes=== + Location: Gmail Chat + + Chaired by: Leo + + Notes by: Praveen + + * Asked Leo what apiproxy is. I encountered apiproxy in the source of gaeunit. He explained apiproxy is like a mapping from a function to a function to which it stubs out or replaces. + * Told Leo that I do not want to use gaeunit and rather write my own code for melange. Leo suggested to study gaeunit and see how they do the magic. + * Asked Leo a couple of questions regarding TaskQueues and the meeting concluded with Leo asking me to explore and explore and learn. + +==Monday May 30, 2011 == + +===Notes=== + Location: Gmail Chat + + Chaired by: Leo + + Notes by: Praveen + + * Reported my initial research regarding gaeunit to Leo + * We discussed about how to handle the requests by the browser as there is a time restriction on a process in GAE. + * gaeunit does not use TaskQueues and so Leo suggested that the other way to handle the requests would be by using a JavaScript. But I did not find any JavaScript in the code of gaeunit. + * Since my main project is on testing, Leo put before me two options to choose from i.e to finish the online runner in a week or treat it as a side project and start testing. I chose to finish the online runner as I had already spent lot of time studying about it. + * The conference call was suspended for the week. + +==Monday June 6, 2011 == + +===Notes=== + Location: Gmail Chat + + Chaired by: Leo + + Notes by: Praveen + + * Told Leo that I have written the code for the online test runner and that it needs debugging. + * Leo looked at the errors and told me that Nose uses some modules which are restricted by GAE. So we may have to try other options to make the runner. + * The decision was made to write our own runner with the help of methods in unittest module in python. + + During: Melange Conference Call Chaired by: Sverre Notes by: Praveen + + * Told Sverre that I have been working on the online test runner in the week. + * Sverre asked me to take it as a side project and start working on the Testing project now as the time is passing by. + * Leo gave me two days to work on the test runner and finish the work which I started. If I am not successful, start testing. + + +== Wednesday June 8, 2011 == + +===Notes=== + Location: Gmail Chat + + Chaired by: Leo + + Notes by: Praveen + + * Informed Leo that I have finished writing the code for the online test runner and that the runner works on the local instance only. + * It does not work on the live instance because our tests make use of gaetestbed library which imports mail_stub from appengine library and mail_stub can not work on a live instance as it starts a subprocess which is not allowed. + * Leo asked me to start testing. + + +== Friday June 10, 2011 == + +===Notes=== + Location: Gmail Chat + + Chaired by: Leo + + Notes by: Praveen + + * Told Leo that I started working on testing today. + * I asked him if every module in app.soc.logic needs to be tested. He told that all the non-trivial modules which are used presently needs to be tested. + * I told him that I will start with the easier modules like soc.logic.tags, soc.logic.system etc. + + + = Coding Plan =