Which testing should I use for testing #.net windows application

Question

1.00/5 (2 votes)

See more:

Hi ,I am Migrating one of Delphie application to C#.net windows application.

i want to do testing for all the methods ,functions and controls.
which testing should i use and Why.
Is their any tool for testing all the methods and functions of c#.

What I have tried:

i have tried Nunit but i have some method with list having many objects in that ,i was unable to do testing with list objects.for one particular object we can do but for so many objects i was unable to give assert.

Posted 2-Aug-17 0:38am

Member 13341402

Updated 2-Aug-17 19:27pm

Add a Solution

Comments

Kornfeld Eliyahu Peter 2-Aug-17 6:49am

Visual Studio has Unit Test Projects (different templates) - use them if you have no knowledge of any other...
https://docs.microsoft.com/en-us/visualstudio/test/getting-started-with-unit-testing

GrpSMK 2-Aug-17 10:22am

Try unit testing in visual studio first..all the best

BillWoodruff 3-Aug-17 0:10am

Sounds like you are "giving up" on testing without really doing research on the testing tools available for .NET.

If you ask specific questions, and give specific code examples ... we can help you.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RickZeeland · Answer 1 · 2017-08-02T06:40:00

Solution 1

It depends on the complexity of your solution, we have a big and complex solution with over 200 projects and our development team is small (5 developers max).
We found that it took too much time to maintain the Unit tests (with Nunit), in fact we seemed to spend more time on this than on productive coding alltogether.
We totally abandoned unit testing, but we have a tester (totally overworked) that tests the main Windows product manually.
So my advice is: unit testing is not worth the time and effort if you are a lone developer or in a small team !

Posted 2-Aug-17 6:40am

RickZeeland

Comments

BillWoodruff 3-Aug-17 0:15am

Interesting, Rick; while I am not a 'strident' devotee of TDD, I feel like testing does have an integral role to play, particularly for large projects. imho, it's not the sheer number of tests (the myth of complete code coverage ?) that is critical; it's creating the critical tests that is the challenge.

RickZeeland 3-Aug-17 3:04am

That's a good point about the critical tests, and for me that was also too big a challenge as they expected me too write unit tests for code written by others that was not documented and incomprehensible !

Zahid Mughal · Answer 2 · 2017-08-02T19:27:00

Solution 2

You may use

Lrmis.Web.UnitTests

for testing purpose, which is very useful and popular in .Net

Posted 2-Aug-17 19:27pm

Zahid Mughal