Testing an Azure device Function: Can't create an instance of TraceWriter, how to taunt?

Question

I am trying to unit test to use the basic Azure function. The Run function requires the argument TraceWriter; TraceWriter is an abstract class, and I'm not very good at documentation for bullying this dependency.

Here is the signature of the method I'm trying to verify:

public static void Run(string myQueueItem, TraceWriter log)

I can simply remove TraceWriter during testing or create an overloaded Run method, but that would be a clear violation of good testing practice. Any ideas for bullying TraceWriter and / or Azure block testing strategies will be appreciated.

Answer 1

Azure ILogger GitHub: https://github.com/Azure/Azure-Functions/issues/293

---

, , VS2017 Preview, , . Azure :

https://blogs.msdn.microsoft.com/appserviceteam/2017/03/16/publishing-a-net-class-library-as-a-function-app/

, , #: https://blogs.msdn.microsoft.com/appserviceteam/2017/03/16/publishing-a-net-class-library-as-a-function-app/

, . , :

Azure TraceWriter

ILogger