I had a discussion today about the name “unit testing”, and its connotations. I’d like to remind you, dear reader, that the audience of this blog is already aware of the goodness that comes with unit testing. Unit testing is part of our day-to-day work, and also for people just starting to get interested in
Sometimes things I do actually work.So I thought of putting them in writing. Best case scenario, you, the reader, might get something out from them. Worst case – I made you laugh or just feel pity. It’s a win-win either way. There is an overarching theme here: process analysis. These are things that I become
After the LIDNUG presentation, we stayed online to discuss unit testing experiences. A couple of things stayed with me from that talk. One: we’re (we developers) are obsessed with tooling and technology (you didn’t expect hard news here, right?). Our main focus should be about solving the business problem first. But, us geeks, we like
I’ll be presenting on the next LIDNUG’s online presentation, Thursday, July 22nd, 11:00AM to 12:30PM PDT/PST (GMT-8). My presentation will be about “Unit testing in the wild”. I’ll show how to test real code, that happens to be in real life. Expect the unexpected. Ok, and code examples in different technologies, like SharePoint, WCF and
Time to see the difference between Moles and Isolator code. Let’s start with the code under test (a webpart): public class NewMessagesCountWebPart : WebPart{ private Label lblNewMessages; protected void CreateChildControls(int i) { CreateChildControls(); } protected override void CreateChildControls() { lblNewMessages = new Label(); lblNewMessages.Text = GetMessageNumberText(); this.Controls.Add(lblNewMessages); base.CreateChildControls(); } private string GetMessageNumberText() { using (SPSite site = new SPSite(“http://sharepoint.typemock.com”)) { using (SPWeb web
Last week, I gave a presentation at the Israeli SharePoint user group on unit testing SharePoint applications. Slides below. Me closer (lurking in the shadows). As an objective observer, I compared the two and only alternatives for Isolation frameworks for SharePoint: Typemock Isolator and Microsoft Moles. And here’s my objective decision: Isolator wins by a
I’ll be presenting (in Hebrew) on unit testing SharePoint apps this Wednesday. More information here.If you’re interested in the topic (SharePoint., unit testing or both), come one, come all.
After my last post, I got some feedback, that I didn’t really answer the question in the title. So I’m going to fix that. Roughly speaking, 10% of developers are doing unit testing today (Let’s call them group A). Some 15% have heard or tried (B), and the rest don’t even know it exists (C).
Running the panel at the Typemock Academy was a great experience for me. (Read: I’ve got loads to learn about running a panel). We wanted to make things interesting, and picked a topic that at its heart not so controversial. But when you dig in, it really exposes a problem: If unit testing has been
Is man destined to choose the quick and dirty road, throwing away long term benefits? While the answer is probably yes (we’re all lazy like that), two dissimilar events in the last week made me think – maybe that’s not the right question. Maybe we need to check how long term are we talking about.