Problem:

I get “no suitable method found to override” errors when I mole system.dll.

Solution:

Modify the System.moles file in your project and exclude everything except the types you are trying to mole.

Explanation:

I was trying to mole the SerialPort class in System.IO.Ports. After adding the mole for System.dll I began to get “no suitable method found to override” errors.  To resolve this issue I simply double clicked the System.moles file to open it in my IDE.  Then I modified the file so that moles were created only for the types under System.IO.  Change System.moles from this:

<Moles xmlns="http://schemas.microsoft.com/moles/2010/">
  <Assembly Name="System" />
</Moles>

to this:

<Moles xmlns="http://schemas.microsoft.com/moles/2010/">
   <Assembly Name="System" />
   <StubGeneration>
      <Types>
         <Clear />
         <Add Namespace="System.IO!" />
      </Types>
   </StubGeneration>
</Moles>

Problem:

I am not getting code coverage results in my build.

Solution:

Ensure you have a test settings file selected in your build definition.

Explanation:

On the process tab of your build definition expand the Automated Testing section under Basic and make sure the TestSettings File is pointing to the test settings file that has code coverage configured.

You can watch a video below that demonstrates how to do this.

 You can view a web cast I did on dev tools here:

Visual Studio/TFS Video Archive  |  Imaginet

For those that wanted the demo code I presented today in the Web Cast it is here. It includes the code to databind a Coded UI Test.

Thanks for joining me and I hope you enjoyed it.

Demo.zip (408.41 kb)

I have gotten some great feedback from the early adopters of Neptune and have begun development on a new version.

The most significant new feature is a POP3 interface so you can point Outlook or Outlook Express (or any POP3 Mail Client) at port 110 and see all the messages in Neptune. This will remove the need to open the trace.log file to view the contents of the processed messages. I noticed also while creating the POP3 interface that Outlook 2007 deviates from the SMTP standard by adding a space after ‘FROM:’ in the MAIL command and after the ‘TO:’ in the RCPT commands. Neptune was updated to handle this deviation.

The next idea is to allow Neptune to fail on purpose and return error codes so you can test your exception cases.

Please add comments with other suggestions for the next release.

Thanks for the support and continue to spread the word.

While working on a current project I found myself faced with testing code that sends email.  In the past I would end up with an inbox full of test messages or unhappy customers that wonder why they just received a flood of emails from my site.  I was also frustrated that there was no way to easily automate this testing.

Enter Neptune. Neptune is a SMTP Development Server targeted for use in automated testing. I simply asked the question, “what if I had a SMTP server that did not relay the message and allowed me to query for messages and their content”. I would be able to use a server of this type to act as my SMTP server during testing and write custom plug-ins, validation and extraction rules to communicate with the server.

The goals of Neptune were to facilitate automated testing and be easy to use. I did not want to have to install a service or understand everything there is to know about running a SMTP server. I simply want to start Neptune and run my test.

Full documentation on how to use Neptune is provided in the msi you can download here. NeptuneSetup.msi (1.27 mb)

If you find Neptune usefull feel free to Donate for future development.