Welcome to MSDN Blogs Sign in | Join | Help

November 2008 - Posts

Monday, November 24, 2008 7:29 AM

My username in OneNote is usually not simply the text John Guin

We were performing some shared notebook testing recently and someone noticed that an outline in one of our notebooks had changed. She first thought that some garbage text had been inserted instead of a typical user name for the text of who last modified
Posted by JohnGuin | 2 Comments
Filed under:
Thursday, November 20, 2008 7:31 AM

Using HyperV to help testing in OneNote - an immediate benefit to me

So the other day I had the chance to head out and work from home. I was able to do this because I had all my testing ready to go in HyperV. I had a Vista Machine with 64 bit version installed ready to go for some setup testing, and had another image ready
Posted by JohnGuin | 1 Comments
Filed under:
Monday, November 17, 2008 7:27 AM

An "Undo" test exposed the smallest amount of time the OneNote automation system knows about

One of our automation scripts was failing last week. The test it was performing is very easy to describe: it pasted text on a page and verified the text was pasted. Then it called Undo to undo the paste and verified the text was indeed gone. And it started
Posted by JohnGuin | 3 Comments
Filed under: ,
Thursday, November 13, 2008 11:55 AM

Robinson Crusoe and OneNote: short term vs. long term gains when testing

I have a theory about the value of automation (and many other test tools) and the time it takes to develop, maintain and use them. I call this my "Robinson Crusoe Theory" of testing and it goes like this: Imagine you are cast away on a deserted
Posted by JohnGuin | 4 Comments
Monday, November 10, 2008 9:03 AM

OneNote Merge Testing - an example of "not a bug, it's a feature"

Last week Mike and I were performing some merge testing. "Merge" is the word we use to describe the behavior of taking my changes and Mike's changes on a page in a notebook and merging them together. For instance, if there was a table on the
Posted by JohnGuin | 1 Comments
Thursday, November 06, 2008 7:26 AM

How my old Microsoft 8-bit BASIC coding skills caused me to fail a code review

I submitted some changes to an automation script a few days ago and failed my code review. Code reviews are the mechanism we use to ensure we all adhere to coding guidelines - Pascal Casing vs. camel Casing, for instance. A peer will look over my code
Posted by JohnGuin | 10 Comments
 
Page view tracker