Unit Test Dependent Methods

Question

0.00/5 (No votes)

See more:

I have created a test project for unit testing the methods in my c# project and various test methods in it. In actual method, there are global class level variables used whose values are set from constructor or other methods. So when actual project runs, the variables have value when referenced in method. Now when I run test for test methods it directly calls the actual method with supplied parameters, but then it will not get the value of global variables, instead getting null.

So my question is that is it possible to unit such kind of methods, or only standalone methods can be unit tested? If yes, then how?

Thanks in advance. :)

Posted 2-May-13 1:30am

Gautam Raithatha

Updated 2-May-13 1:34am

v2

Add a Solution

1 solution

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)

tumbledDown2earth · Answer 1 · 2013-05-02T02:02:00

This is a classic case. You can make the global dependent variables in a config (or some container class) which implements an interface. Now in the live example implement your interface with a config reader class and your methods should read these values from the interface only.

You can create a property (or setter method) so that you can inject a test implementation

Now while testing you can create a test implementation and set the property with the implementation and then your methods should work the same way.

Here is some example code:

C#

public interface IPlayer
    {
        string Name { get; }
    }

public class Player : IPlayer // this class is your live class -- use a similar one in your test
{
     private InputManager inputManager;

     public Player(string name)
     {
         Name = name; // dependency inject or read from config
     }
}

let me know if you need more code to understand