First Peek– Code Review

Update: New version uploaded, same link with:

Small dots in text of error pane – identify the error better.

Multiple Verifies – new rule

Fixed bug recognized TestInitialize as a test – Thanks Dennis!

Fixed bug recognizing loops logic in non tests

Also, for those not downloading in Chrome (and you know who you are), remember to change the suffix from zip to vsix.

Time for another preview! This time it’s a NEW PRODUCT!

Internally we call it Unit Test Code Review. And the name is really self explanatory.

It’s a VS 2010 extension (double click on the file and it installs). It’s very simple – the test code gets parsed, and analyzed according to rules. When a rule is broken, the offending line is marked, and an error appears in the Error List window. Double-click on the line, and you’ll get more information about the error, including a link to a corresponding webpage. No need to compile – it runs in the  background.

Installation instructions:

• Double click on the vsix file to install it on VS2010
• Go to Tools->Options->Environment->Extension manager, and make sure the Load Per User checkbox is checked.
• Restart VS. (the final 2 steps are needed only once).

The currently supported rules are:

• No Asserts – There’s an error if in a test there is no Assert. If however, there’s an ExpectedException attribute on the test, it’s smart enough to know that an Assert is not needed, and you won’t get an error
• Multiple Asserts – Means you’re testing too much. There’s no error if you’re testing multiple asserts on the same objects, only on multiple objects.
• Avoid logic – If you’re using an if/else or switch/case in your test, this error pops.

We’d like to know what you think, and what other rules you think would be beneficial.

You can download the installation file here. Tell us what you think!

Help with Twitter Campaign

Hi Guys, hope that you had a great weekend

I’m Tal the new Internet Marketing manager at Typemock, Pleasure to meet you …. ;)

I just wanted to give you guys an update about the Twitter campaign that we are running this month, in order to get as many twitter followers. We’ve just started last Friday and we’ve already got 340 – and we want many more!

We are having a sweepstake every Wednesday, between all the people that are following us on twitter, all they need to do is to start follow and to twit to their followers that they just entered a drawing to win Isolator etc..

We’ll appreciate it if you can twit/blog/shout in the street about it as well. We’ve already gave one free license, and we’re planning on giving a license every week until the end of February.

Thanks in advance!

Unit Testing Community – Conference Call Monday

Hi Guys,

Most of you have been in the loop, but for those who haven’t, here’s a short recap -

We want a community for people from all technologies, not just .Net, come to discuss all about unit testing – from tools, to practices, to implementation. Everything unit testing. We thought about doing a StackOverflow Q&A thing, but we’re open to anything you might suggest. Note that this is not a Typemock venture – it’s by the community, for the community.  We are prepared to contribute the site (we have the domain www.assertfailed.com we can park the site under), and we’re willing to contribute some money for the development and maintenance. But mostly, it is going to be a community venture.

Our goal - get a live site up in the air by Feb-28th. It’s time to move on, and I’ve set up a conference call to discuss it on Monday February 1st at 2pm UTC (Most of the people interested were from the Eurpoean time zones, but I assure you, that’s not the last conference call we’ll have). The Go-to-meeting link for the call is here, see details at the bottom.

I’ll keep everyone in the loop here for the time being, until we have all teh communication infrastructure ready. We’re going to discuss what we can do in Feb do achieve the goal, and what Typemock can help do.

See you tomorrow!

----- GoToMeeting Info ----

Meeting ID: 541-806-066

Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

Australia: +61 (0) 7 3123 6030

Austria: +43 (0) 7 20881407

Belgium: +32 (0) 28 08 4297

Canada: +1 778 785 0724

Denmark: +45 69 91 88 70

Finland: +358 942 599 697

France: +33 (0) 182 880 463

Germany: +49 (0) 892 2061 169

Ireland: +353 (0) 14 845 983

Italy: +39 0553989569

Netherlands: +31 (0) 208 080 385

New Zealand: +64 (0) 4 974 7216

Norway: +47 21 04 29 13

Spain: +34 955329911

Sweden: +46 (0) 313 613 559

Switzerland: +41 (0) 225 3314 55

United Kingdom: +44 (0) 203 318 4725

United States: 626-521-0010

Access Code: 541-806-066

Audio PIN: Shown after joining the meeting

 

GoToMeeting®

Online Meetings Made Easy™

Preview of next Isolator release

Hi guys,

This is an early preview of the version we’re releasing towards the middle of January. The major featrues are:

• Single installer for 32 and 64 bit! now you don’t need to choose!
• Support for VS2010
• Support for .Net 4.0, including VB support, which gave a bit of a challenge. We’re supporting dynamic data types and optional/default parameters. Something like that:

[TestMethod]
public void WhenCalled_OnDynamicFake_ReturnsChangedBehavior()
{
   dynamic fake = Isolate.Fake.Instance<UnderTest>();

   Isolate.WhenCalled(() => fake.GetValue()).WillReturn(1);

   Assert.AreEqual(1, fake.GetValue());
}

In addition, there a few bug fixes:

• Configuration.dll was not installed to GAC in auto-deploy.

• Fixed "Explorers and Designers" package load failure

• wrong exception thrown from Isolate.Invoke.Method

• new bug in 5.4.5 caused multiple calls to set on indexer throw null reference exception

• new bug in 5.4.5 caused access to properties from base types to throw null reference exception

There are a few days left until the official release, but you can enjoy it now before everyone else, by downloading it here (note, it still has the same version number 5.4.5).

Ivonna.WCF is coming

Hi Guys and Gals,

I plan to develop a new tool for testing your WCF services. I've got very little experience in WCF (although it was enough to realize that I need a testing tool), so I'm asking for suggestions. What do you usually need to test when working with WCF?

For example, when I just got started, I used code copypasted from various sources. All I was getting was 404 Not Found, while the problem was that the server and client parts were configured differently. Wouldn't it be nice to have a test that would reveal that problem and provide a suggestion on how to fix it?

This new tool would use some core functionality of Ivonna, however, it would be a different product. Ivonna will be refactored into the core assembly (used in this WCF tool) and the WebForms-related piece. Perhaps this new product would be given a new name. So, I'll be happy to hear your suggestions!

Thanks for your help
artem