Unit/functional tests and continuous integration

[Shakthi Kannan]

Hi,

Few more suggestions:

In Test Driven Development (TDD), we write test cases first, and then
write the code to make the tests pass. So, when using Agile
methodologies, I urge you to write unit/functional test cases. This is
helpful:

- As it gives motivation for you to write code to pass the tests.

- Setup continuous integration [1] builds that re-run the test cases
at periodic intervals, to make sure one hasn't broken anything. If
anything breaks, the result of the tests should be sent via e-mail to
the list, or the concerned team members.

- When you refactor code, you can re-run the tests to make sure your
logic hasn't been affected.

- Please use rails_rcov [2] (or any other related tool) to see the
code coverage of your test cases.

- In a production system, you can run these test cases on the test
database to make sure everything is fine, before switching to the
production database. This can save you lot of time troubleshooting
problems, if there exists any.

If you are looking for specific gems, you can refer the Ruby Toolbox
[3]. Bookmark the same.

SK

[1] Continuous Integration.
http://martinfowler.com/articles/continuousIntegration.html

[2] rails_rcov. http://agilewebdevelopment.com/plugins/rails_rcov

[3] Ruby Toolbox. http://ruby-toolbox.com/

-- 
Shakthi Kannan
http://www.shakthimaan.com

[Gaurav Menghani]

Hi,

I highly appreciate the valuable inputs you have been providing for the
betterment of the project. 

In the proposal which I submitted for this project [1], I have assigned
the period from 12th of July to 8th of August as the slack period, where
the bulk of testing can be done. This was done so as to conform to the
'90%-working-by-midterm-evaluation' principle.  

Since, I still have a lot to learn about Ruby-on-Rails, and am not
familiar with testing tools in RoR, it will take me some time to grasp
that and put it into practice. Moreover test cases would need to be
written for almost all the features. Thus, I would like to follow the
schedule and conduct the testing as per the plan.

Please let the suggestions coming for improving the code and the
project.

Warm Regards,
Gaurav Menghani.

[1]
https://fedoraproject.org/wiki/Summer_Coding_2010_proposal_-_Four_Seasons...

[Shakthi Kannan]

Gaurav:

--- On Mon, Jun 28, 2010 at 5:23 PM, Gaurav Menghani
<gaurav.menghani(a)gmail.com&gt; wrote:
| In the proposal which I submitted for this project [1], I have assigned
| the period from 12th of July to 8th of August as the slack period, where
| the bulk of testing can be done. This was done so as to conform to the
| '90%-working-by-midterm-evaluation' principle.
\--

My suggestions, are suggestions. You could incorporate them in future,
or whenever time permits. Rails coming from Agile methodologies,
follows these practices, and it will be good for you to learn them
during the project. After all, it is part of the experience.

---
| Since, I still have a lot to learn about Ruby-on-Rails, and am not
| familiar with testing tools in RoR, it will take me some time to grasp
| that and put it into practice. Moreover test cases would need to be
| written for almost all the features. Thus, I would like to follow the
| schedule and conduct the testing as per the plan.
\--

You must follow the instructions given by your mentor, Shreyank, and
the Fedora Summer Coding guidelines.

---
| Please let the suggestions coming for improving the code and the
| project.
\--

I didn't want to send a stream of e-mails and scare you, and hence, I
am pacing my e-mails.

Regards,

SK

-- 
Shakthi Kannan
http://www.shakthimaan.com