RockyCode

In NUnit, you can specify a category on a test method or test fixture. I needed that list in a totally different context. Here's how to do it.

The default triggers provided by CruiseControl.NET just didn't fit my unique scenario. I needed a trigger that could check a database table, and if rows exist - to force a build. Check the low down...

I have several machines where I run CruiseControl.NET for our test automation. Today, I went to look at the results and I would get a 404 error on one of the boxes. I checked another machine and the build results would come up just fine.

We have a custom object called ListOption in our code. It holds category, value and option and fairly represents the basics of a single SelectList item. To hold the ListOption values, the primary developer stored this List as and IList instead of an ArrayList or any other concrete type. OptionList extends IEnumerable.

Here is how I sorted the IList.

The CategoryAttribute can be used to specify additional groupings of test cases that you want to run at the same time. For example, we have our test cases split up into level of priorities (Level 1, Level 2, Level 3). Here's how you can do it:

With a couple thousand tests, the email can be pretty big when viewing the results. We decided we only wanted the high level summary rather than the nitty gritty details.

One of the applications I am testing deals a lot with finance information. However, since most of the data is stored in a remote database, I can't collect or check all the data I want to. We only store a fraction of this information in our schema. I had the wsdl files from the finance department in order to make web service calls. Here's how I did it.

I was trying to automate some tests that included a PDF loaded inside an IE 7 window. Using conventional methods, I could not attach to this new window, thus couldn't control whether it was done loading, or close it for that matter.

After upgrading to the latest version of CruiseControl.NET (1.4.4.83), and then inserting the custom xsl back in, I could not expand the details to view the test results.

On our project at work, I am experimenting with some lambda and linq expressions. It's been kind of fun except for the road-block I hit.