Tag Archives: uncle google

Google Apps: Migration to New Services

As of yesterday, I had two Google accounts: my irrsinn.net Google Apps account and my regular ol’ Google Account. Both had the same email address, but the Google Account let me into services like Reader, Voice, and Feedburner.

Having two accounts was annoying, but not unbearable. It meant that Google Voice, for instance, had none of my preciously-maintained and iWone-synced contacts. I just created contacts within Voice as calls came in, no biggie, but I’ve definitely been using the service less as a result.

Turns out that Google’s been working on this, and recently added a boatload to services to Google Apps users: Voice, Feedburner, and Reader being the three I’m more interested in. AdSense was tricky, and was only moved for posterity. Continue reading Google Apps: Migration to New Services

Excluding Hits from Google Analytics

If you want to exclude your own visits to your site from Google Analytics on a per-computer or per-session basis, searching will land you on Google’s help page: How do I exclude internal traffic from reports?. Problem is, the code there doesn’t work with Google’s new-ish asynchronous tracking code. There is no “pageTracker” object any longer, so that’ll throw a nice little error.

The replacement for “pageTracker” is to push the custom variable onto the _gaq object, per the new standards.

To get this working, make a new, simple HTML page, just including the basics to make the page validate. Include your standard-issue Google tracking code in the head, like so:
Continue reading Excluding Hits from Google Analytics

Unit testing — staring at a blank screen

For all the brouhaha about unit testing and Test Driven Development, I have yet to find a guide — book, website, anything — that actually discusses how to write unit tests.

There are nUnit-specific articles that talk about the foibles of each and how to have testing run constantly and so on and so forth, but how do I know how to compose a unit test? How low-level and nitty-gritty do tests need to be so that they’re useful without making me want to stab myself in the eye from maintenance? What’s the best way to test controllers vs. models?

Maybe I’m just not cool enough with Uncle Google to find what I’m looking for, and I certainly don’t mind experimentation, but I’d be interested in hearing how the “experts” approach TDD.