Watch out! The Telerik DevCraft Q3 2012 “What’s New” Webinar Week is fast approaching! Free your calendar for the week of October 22-26, 2012 and prepare for five days packed with information-rich webinar sessions explaining all the cool new features we have developed for you in the past 4 months.  Are you ready for Windows 8 and Visual Studio 2012? DevCraft is here to help you explore and take advantage of all the new opportunities that come with Win8 and VS 2012. Let us help you get there! Book your seat for Webinar Week now! As always, each attendee of Telerik’s Webinar Week...

Technorati Tags: TDD,Test Driven Development,JustMock,JustCode,NUnit,NUnit.Should,Mocking Before diving into mocking with JustMock, it’s important to note that JustMock is a mocking framework, and not a testing framework.  Test frameworks allow for creating Test Fixtures, which are .NET classes decorated with the appropriate attributes so they are picked up by a Test Runner.  Test are created within a Test Fixture by writing methods (with the appropriate attributes) that exercise your code (also referred to as the System Under Test) and report the results.  Test Runners are programs that will run your tests.  There are many free testing frameworks available for .NET developers, including MSTest (included...

We, the OpenAccess ORM team, believe that an ORM solution should not only be easy to use and time-saving, but also flexible enough to reflect your needs. For instance, it is important that the names we generate comply exactly with your conventions, rather than being enforced. For that purpose we have provided the Naming Settings dialog a while ago, offering various naming options for the model on Class, Property and Field level. Now we are proud to present the new flexibility we have exposed for generating the names of the tables and columns in your database - the Database Names...

Test Studio’s IF Conditional steps are extraordinarily handy feature which enable you to handle branching in your tests based on specific conditions. There are a number of scenarios where this can ensure your tests are a bit more robust—logging in to your system if needed is one example. (Note: There are also many situations where I recommend against using conditionals. Don’t use them to conflate separate test cases. Keep your test cases simple, specific, and granular!) Here’s a tip I just learned today: Editing an IF conditional’s verification. This is nice feature because it allows you to update your conditional ...