Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am developing a web portal in asp.net 3.5 which is mainly a front end for various other links and web forms developed else where. There is not much business logic except some CRUD operations to the database and fetching data. And javascript, Jquery for user interface.
In this scenario, is unit test necessary and is it required to test the javascript also?
Unittesting is not required to get something going, but as you start testing I hope that you see that it is crucial for maintaining a large code base.
Right now your app is small, and a user can easily verify that it is working. ie. Go to a page, submit a form, make sure that the form is posting correctly, make sure that the database is saving the correct information.
As your application grows, or as you begin to build on your CRUD operations it will be crucial that they are correct and that you can test them programatically, testing your code now sounds like it would be trivial, and therefore with the effort, because of the time it saves in the future in regards to refactoring your code or hunting down bugs.
Qunit is a great simple javascript testing framework http://docs.jquery.com/QUnit