Didn’t get as much done as I would have liked. Though one thought did cross my mind why do VS templates not conform to things like StyleCop and R#
Must admit though I like Pex as it helps create tests I think I might need to pick a fresh project to add it to.
Do take the time to read through the documentation and the slide decks are good for teams.
I have a class that I need to serialize out for remoting which has information about an order with addresses, payment details and order items.
This object will be sent to a message queue and deserialized before process into out MS Dynamics Nav database.
The first thing I did was download the latest version of Pex and get the class to build. Once this was done I ran the Pex explorations and encountered an error ‘failed to generate project CSharp\Test\TestProject.zip’ the post explains about file path lengths and how to get passed this. It’s a bit confusing here as this was my home machine and it’s not difficult to move solutions around but I think it my be more tricky on the dev box at work where paths can be long as projects can be nested quite deeply. This has also caused Reshaper to throw exceptions as well so it is something to watch out for.
So what happened next – well everything went smoothly and Pex found that I was missing an entry in my app.config. True – i had copied the code over but not the solution so I had missed the app.config even though everything built. A .stubx file is built by default for the class under test.
It is worth pointing out that I had seen previous demos of Pex at DDD7 and read through, though so far not in great detail the documentation.
I’ll go through the other tests tomorrow.
Just run the Bowling Game application created to run unit tests from the TDD book and used Pex to create parameterized unit test stubs and it creates a .stubx for each of the classes. Wondered how each class had to be stubbed out.
Should have paid more attention to the ‘Getting Started’ document where it mentions that Stubs only supports mocking of Interfaces and abstract methods.
Pex 0.13 Released with this release and some new project work I’m going to try and use Pex to create tests. Should be interesting as I’ve got to test webservices and serialization for messaging.
MOSS SP2 Expiration Issue there is an issue where the expiration date on an SP2 updated server will as they say “During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users.”
How’s that for an issue!!!
