Unit Testing Asp.net server control

Hi

1.I am familier unit testing the cs file, business logic and methods using VS 2008. We developed a Asp.net Server control and I am confused by how to unit test the Server control. Along with the business logic(ie methods in the control), how to unit test the UI(front end) and how to make the report is there are any discrepancies. How is unit testing the methods different from unit testing the UI.

2. Unit testing the ui means, just checking whether the ui is in accordance with the design document or fsd?

3.Is there any generic format for making the test report that includes test results. Could anyone please suggest/post some resources on this.

Thank You
mkarthik415Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

rockiroadsCommented:
if your familiar with testing then you should use the same principles

for business acceptance testing you need to ensure that where ever that control is used it does not affect the business rules, allowed input, expected output, page flow etc

you would unit test that, there is a tool called nunitasp which might be handy for you. you want to make sure all the methods work as expected both positive and negative testing. unit testing is not just about the design document. you want to try break it and ensure your code can handle it, right error messages displayed etc hence the negative testing

for test reports/results etc is there no standard format your company uses?

typical things you would need for a test plan

test number, classification, platform, s/w version, test description, details of any inputs, expected outputs, method of test (manual or automated)

and the test results would fill in those details along with pass/fail, comments, date test ran, name of tester etc

There are tools out there that help with capturing this info like Quality Center but that costs money.


something here you may find useful

http://msdn.microsoft.com/en-us/library/dh9ad08f.aspx
http://aspalliance.com/1328_ASPNET_OOP_and_Unit_Testing.all

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.