Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve been playing around with .NET SpeechSynthesizer lately.
and I’ve got a method that takes in a string and creates a .wav file out of that string.
but how do I unit test this method ?
seems to me like this situation is one in which unit testing cannot help you. am I right ?
What do you want to test here?
Does the .NET SpeechSynthesizer API write the wave file or does it output something to your code which writes the wave file?
Testing this is the same as testing any other dependency. First isolate it (thin & mockable wrapper arround the NET SpeechSynthesizer API). Then validate your code gives the wrapper what you think it should be given and acts on any returned data the way it should act. Leave testing the .NET SpeechSynthesizer API to someone else (the creators of the API).
Testing the wrapper is an intergration test (don’t let the name stop you from doing it in a TDD manor if thats your thing), and you will likely have to be quite loose on what you validate (“Speak(string) causes the output file to grow”). But again you don’t need to validate the API works.