<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><div>hi,</div>
<div> As I earlier sent you mail that i am improving my application as it</div>
<div>was very roughly written. Mr.Daniel (ajax) Diniz helped me alot for this <br>so that it could be easily readable for the mentors.I am also attaching </div>
<div>my old application with this mail.So please give me suggestions for </div>
<div>this application so that i can improve this more.</div>
<div> </div>
<div><br> <span style="font-weight: bold;"> </span><font style="font-weight: bold;" size="3">Enhancing Core-Python Testing Infrastructure</font><br><br><span style="font-weight: bold;">Abstract:</span><br>The aim of this project is to make testing easier, more efficient and<br>more useful for core Python development. This can be achieved by:<br>1) Creating a bridge between the core Python Testing Infrastructure<br>and the nose framework[1], which provides many desirable features,<br>including simple test writing and running, tag-based test filtering,<br>code coverage reports and extensibility with plug-ins.<br>2) Providing a smart GUI for nose, to make running the tests easier.<br><br><span style="font-weight: bold;">Content</span><br><br style="font-weight: bold;"><span style="font-weight: bold;">Summary:</span><br><br>1) Python is improving each day by providing more features and<br>facilities to python programmers, but core
Python developers don't<br>have a full-featured testing infrastructure. Their expertise allows<br>them to write their own mini-frameworks to cover missing features as<br>needed. New developers have to learn each different testing style to<br>be able to test and debug the code they change, which is a problem. I<br>think a good testing framework will solve this issue. The nose<br>framework is a good option for making the Python Testing<br>Infrastructure better. It allows to selectively execute certain tests,<br>capture their results and collate error output. It can also add<br>coverage and profiling information in addition to finding and running<br>the tests. Another important feature of nose is its plug-in based<br>architecture, which allows extending its features set easily. However,<br>nose isn't presently compatible with the core Python test suite.<br>Adding a compatibility bridge can be done by writing a nose plug-in<br>which will allow nose to
execute the core Python test suite. This way,<br>all great nose features will be available in the core Python Testing<br>Infrastructure. This will provide great help for easier bug<br>confirmation, fixing and testing. Since tests will be more relevant<br>due to finer-grained control (e.g tag-based execution), it will also<br>help in reducing running time of tests and avoiding accidental<br>disabling of tests.<br><br>2) GUIs ease the use of applications, specially for new users who<br>don't know the application well. Those who are new to testing or to<br>nose could be more successful using a graphical interface than the<br>command line interface. This project will provide a smart GUI for<br>nose, with a execution window to run various tests with different<br>options, an editor to help writing tests and plug-ins, and the ability<br>to configure nose based on information like which plug-ins are<br>available. It can change their value. It will also
help to use<br>plug-ins, like tagging of tests using GUI, in case of tag plug-in. We<br>can also enable the logger to view and work with logs in the GUI.<br><br>The final goal of this project it is to implement the new features<br>without changing anything in the core Python Testing infrastructure or<br>in nose. Instead, this project will offer a bridge between nose and<br>the core Python test suite. It will include nose plug-ins and wrappers<br>that will provide valuable features like tag-based execution, code<br>coverage reports and many more. In the same way, I am not going to<br>change the default behavior of python-nose, but write the GUI in a way<br>that it works with the current nose code. The GUI could then be used<br>to provide an easy interface for testers, without a negative impact in<br>command line use.<br><br><span style="font-weight: bold;"> Schedule:</span><br style="font-weight: bold;"><span style="font-weight: bold;"><br><font
size="2">Start of program:</font></span><br><span style="font-weight: bold;">0) March - 20 April:</span><br>I have studied and discussed the nose framework and the core Python<br>testing infrastructure. I have added a command line option to<br>regrtest.py, ... etc. By doing this, I have learned about how the core<br>Python test suite works, its rough organization, how it uses unittest<br>and test_support.<br><br style="font-weight: bold;"><span style="font-weight: bold;">1) 21 April - 14 May:</span><br>I will analyze the nose framework code in more detail, specially the<br>plug-in system, test discovery and runner parts. Then I will analyze<br>the regrtest.py script (test runner of core Python test suite) and the<br>needs of the core Python test suite in depth. By doing this, I will be<br>able to create a detailed roadmap for a set of nose plug-ins and<br>wrappers to make all interesting features available to the core Python<br>tests.<br><br><span
style="font-weight: bold;">2) 15 May - 20 May:</span><br>I will use this time to create a basic layout for a nose GUI nose. I<br>will decide its looks, which features and windows should it include<br>and create an implementation plan.<br><br style="font-weight: bold;"><span style="font-weight: bold;">3) 21 May - 23 May:</span><br>To write tag-wrappers for such a big test suite as Python's would be a<br>problem given the number of tests present, so I will write a small<br>application to do this job. I have to study what is necessary for<br>that.<br><br style="font-weight: bold;"><span style="font-weight: bold;">Midterm evaluation:</span><br><br><span style="font-weight: bold;">1) 23 May - 10 June:</span><br>I will finish the code of the nose plug-ins and wrappers needed to<br>support the core Python test suite.<br><br><span style="font-weight: bold;">2) 11 June- 25 June:</span><br>Test and debug the nose plug-ins to provide code coverage and
sensible<br>results. After that I will clean up the code.<br><br><span style="font-weight: bold;">3) 26 June- 5 July:</span><br>Write “tag-wrapper creator” code and generate desired tags based on<br>feedback from core developers.<br><br><span style="font-weight: bold;">4) 6 July - 12 July:</span><br>Test,debug and clean up code of tag-wrapper creator.<br><br><span style="font-weight: bold;">Final evaluation:</span><br><br><span style="font-weight: bold;">1) 12 July-28 July:</span><br>Code for a nose-framework GUI. I will first work on a execution window<br>for tests, then a configuration window, a graphical view to use<br>tag-wrapper writer, integration of nose plug-ins and test writing<br>tool in the GUI.<br><br style="font-weight: bold;"><span style="font-weight: bold;">2) 28 July-10 August:</span><br>Test, debug and clean up code of the nose GUI.<br><br><span style="font-weight: bold;">3) 10 August-15 August:</span><br>Prepare documentation
on the work.<br><br><span style="font-weight: bold;">About Me:</span><br><br> I am an Information Technology student doing graduation at Punjab Engineering College[2] in India.<br><br style="font-weight: bold;"><span style="font-weight: bold;">My technical skills:</span><br><br>1) I am good in C and C++ programming. I really love C and have a good<br>grip on this language. I also did many college level projects.<br>2) I learned .NET framework and developed one small website as a project.<br>3) I undertook the data-structure course in my college and got 'A'<br>grade in this subject, I am well versed in the concepts of link-lists,<br>trees, graphs.<br>4) I did a course on RHCE to learn Linux 2 years ago and have been<br>using Linux from that time.<br>5) I have taken courses on networking and databases in college.<br>6) I setup the nuclear control system on network of Linux machines at<br><span style="font-weight: bold;">IUAC</span>[3] (a research
center in India).<br>7) I came in contact with Python two months earlier when I was<br>assigned to do a real life project in a research center in India so<br>now presently I have some good knowledge of Python.<br><br style="font-weight: bold;"><span style="font-weight: bold;">My Strengths:</span><br><br>1) Keen to learn<br>2) Creative Mind<br>3) Hard working<br>4) Responsibility<br>5) Ability to adapt circumstances<br>6) Ability to interact with people<br><br style="font-weight: bold;"><span style="font-weight: bold;">Project Motivation:</span><br><br>1) I am new to Python community but I am very keen to learn open<br>source development. I am very hard working and this project is very<br>important to me. I will complete it at any cost as I am planning to<br>pursue research as my career, so this project will provide me a good<br>experience of research and development.<br><br>2) Python is very easy to learn, efficient and I think the
best<br>language. Core Python developers are making the life of python<br>developers easier by providing them very good features within the<br>Python language. This project will allow new core Python developers to<br>be more productive in developing core Python, so the large Python<br>community will get benefits from my work.<br><br><span style="font-weight: bold;">Contact Info:</span><br><br>I can be in touch with mentors and the community via IRC, Email and IM<br>during this project.<br>I have good programming skills in Python and has got good<br>understanding of nose and core-python testing infrastructure on which<br>this project is depended upon.<br><br>[1] http://www.somethingaboutorange.com/mrl/projects/nose/<br>[2] http://www.pec.ac.in/<br>[3]http://www.iuac.ernet.in/</div></td></tr></table><br>
<!--6--><hr size=1></hr> Add more friends to your messenger and enjoy! <a href="http://in.rd.yahoo.com/tagline_messenger_6/*http://messenger.yahoo.com/invite/"> Invite them now.</a>