Implementing Successful Automation Solutions

A couple of weeks ago I was asked to give a quick talk on implementing successful Automation solutions. I tried to come up with something that didn't talk to our solution or tool but more to our experience. Here is the outline of that quick talk. 

The Three Mile Stones

• Gaining Support
• Gaining Traction 
• Maintaining 

 Gaining Support

• Create a solution that becomes a integral part of your comany's software processes. 
• Create a several quick wins (the lowest hanging fruit with the most benefit). 
• Be very visible and open with everything you are doing. 
• Don't spend a long time developing a large framework. 

 Gaining Traction

• Instead of trying to tackle a back log which can put you in a perpetual state of "Working on the back log" draw a line and work along side the developers on the new feature moving forward with them and picking off the back log only  when you have down time or extra resources. 

 Maintaining

• Run test nightly or weekly. 
• Dedicate time out of each week to maintain your suite. 
• Don't let the test sit untouched over a development cycle. 

-Sarah

Iterating through a Html Table

Some of the more common testing we do involves comparing a list of data on the page to a list of expected data from the db. I like to using the following code snippet to accomplish it.
1: for (int i = 0; i < DbTable.Rows.Count;i++ )
2: {
3: for (int j = 0; j < DbTable.Columns.Count; j++)
4: {
5: DataRow dbRrow = DbTable.Rows[i];
6: HtmlCell cellRow = new HtmlCell(contentTable);
7: cellRow.FilterProperties[HtmlCell.PropertyNames.RowIndex] = i.ToString();
8: cellRow.FilterProperties[HtmlCell.PropertyNames.ColumnIndex] = j.ToString();
9: if (!cellRow.FriendlyName.Contains(dbRrow[j].ToString()))
10: {
11: _error += dbRrow[j].ToString() + " did not match " + cellRow.FriendlyName;
12: }
13: }
14: }


In the inner loop you can always offset the row and column if you have a check box in your table or maybe an image you don't want to Compare on. -Sarah