The standard answer is to reverse engineer your class so you can mock the dependency. This is usually done by entering your data source as an interface into your class.
eg. You may have a class that acts like below
class John
{
public John() { }
public void Load()
{
}
}
Download depends on SQLCommand, so you always need to call db for this
,
.
class John
{ IDataSource _db;
public John(IDataSource db)
{
_db = db;
}
public void Load()
{
_db.Load("John");
}
}
, / , . , . , . . , .