Automation cleanup in OneNote

One of the tasks the test team can look forward to completing over the next few weeks is "automation cleanup." Over the last three years of getting OneNote 2010 completed, we’ve overhauled our automation system, added a new "task library" of common code to get our testing completed and have written hundreds of new automation…

6

Working on a verification for printing to OneNote

Spent some time last week working on a script to verify that the printer actually works when printing from an application to OneNote. I learned a little something about our OneNoteOfflineCache_Files that I thought may be interesting as well. I’ll start with that. The OneNoteOfflineCache_Files folder is a stored in the subfolder of the OneNote…

2

A pet peeve of mine when logging values in our automation scripts

  Way back in November 2008 I mentioned a code review of some test scripts.  I remembered something I saw many months ago (more than a year?) and this reminded me I wanted to revisit it.   The purpose of most of our automation scripts is to verify that the functionality we expect to be…

1

Napkin Math script is now passing 100% of the time

  Back in April, I was having a problem investigating a failing automation script.  The script was a napkin math script (napkin math is the lingo we  use for the feature in OneNote that computes simple equations as you enter them).  The failure had nothing to do with the feature in OneNote.  It only failed…

0

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 island. You managed to save a fishing pole,…

4

A better fix for the failing OneNote automation script

  I did not like my code fix for the error detection routine when  trying to detect which file OneNote had loaded twice.  To refresh my memory, here was what I initially checked in:   SortedList<string, string> loadedModules = new SortedList<string, string>(StringComparer.InvariantCulture);   System.Diagnostics.Process onenote = System.Diagnostics.Process.GetProcessesByName(“onenote”)[0];   int i = 0; Console.WriteLine(“There are this…

1

The other bug in our test code for spelling

  Last Thursday I posted some snippets of the code we had been using to automate and verify spell checking had been implemented in OneNote correctly.  Before I could check in the code, there was one other bug I needed to verify did not exist, and the code I posted would potentially have let it…

1

TWIONT is a lousy acronym no matter how you look at it

As I’ve mentioned before, we have been in the process of moving all of our automated tests away from being UI based and converting them to white box tests. The results have been very positive thus far, but it has not been a free conversion – there is a small cost to pay. One of…

1

Automation tasks for the OneNote test team

  Right now we have a little bit of spare “bandwidth” to complete some automation tasks which have been building up over the last few months.  The lingo around here never lets us refer to spare time: we always call someone who has a few free hours to spare as having “extra bandwidth.”  Like every…

3