Name: Himanshu Awasthi

Project Page: Testing_Project

Diary Page: 89hardy_diary

Primary email address: himanshuawasthi9@gmail.com

Secondary email address: 89hardy.code@gmail.com

Blog URL: http://89hardy.wordpress.com/

Trac username: 89hardy

IRC username: hardy_89, hardy89, 89hardy,himanshuawasthi

Contact No:09990939080 Country: India Timezone: GMT+5:30 (Asia/Kolkata)

Academic experience: Pursuing Bachelors of Technology, Major Computer Science, from Maharshi Dayanand University

Current occupation: I'm a Engineering Student, and a Guitar Trainer on weekends.

Software projects already participated in:

  1. Made a face recognition app using Python, as a college minor project.
  2. Studying Flask micro-framework for making a Quote Management System for our IRC channel.

About Me:

I'm a final year engineering student of Computer Science. I started programming 3 years ago with C in the first year of my college. Then HTML, and CSS came in. I shifted to Python 8-10 months ago and never looked back. I attended local geek meetups, PyCon India, technical fests, and various other conferences and events. Further indulged in Pylons and then Flask. I'm also a guitar trainer trying to ensure Rock 'n Roll has a bright future. I also like to read Fiction and Sci-Fi books.

Experience Level:

Experience with Google Summer of Code: This being my first GSoC, I've been aiming for it for past 10 months right from the day I started coding in Python. Numerous hours dedicated to 'Byte of Python' and 'Dive into Python', making small programs and running them, and idling on IRC has become routine since then. Kept adding few more skills like Pylons and Flask framework, HTML, CSS etc. to be able to reach a level from where I can contribute to the organization I work with.

Experience in coding in general: Started in 2007, 950 hours

Experience in Python coding: Started in 2010, 600 hours

Experience in HTML: Started in 2007, 150 hours

Experience in CSS: Started in 2007, 150 hours

Experience in Javascript: Started in 2007, 15 hours

Language I know: Python completely changed the way I write code and flipped it 180 degrees. Everything about this language is amazing and beautiful.

Tools used for development: TextMate, Terminal, Xcode(very rare)

Timeline

Community bonding period:

  1. Get a clear picture of the current bugs related to tests.
  2. Read the documentations of py.test 2.0, unit tests and mercurial.
  3. Read and Run every test individually and compare tests written on version 1.3.4 to version 2.0.3 to track related bugs.
  4. Talk to mentors and draw up a detailed roadmap of the entire project.

June 8 - June 13 (Quarter-Term)

  1. Complete log of the current bugs.
  2. Sanity checks of the tests which need not be re-written.
  3. Tests which cannot run because of minor conditions like missing external libraries will be fixed. 4.Porting of tests from py.test 1.3.4 to pytest 2.0.3. 5.Fixing bugs noticed after porting is completed.

June 14 - July 11 (Mid-Term)

  1. Compatibility of all the tests to py.test 2.0.3 will be ensured.
  2. All tests with minor glitches and which require normal sanity check will now be working.
  3. Test coverage will be reviewed and improvement of state of tests will be done.

July 12 - Aug 1 (Three-Quarter-Term)

  1. Re-write all the tests and make them 'good tests' keeping minimum memory usage in mind.
  2. Review all tests and correct the broken code, if any.
  3. Adding the remaining tests in the package and keep a check on reviews.

Pencil Down Date (Aug 22)

MoinMoin: HimanshuAwasthi (last edited 2011-05-29 16:05:19 by Himanshu Awasthi)