Test Driven Development for a Business Intelligence Project with Crystal Reports: Part 3
page 1 of 7
Published: 29 Aug 2005
Unedited - Community Contributed
Abstract
In the final part of a three-part series on Test Driven Development (TDD) in .NET, Eric Landes shows how to code to the scenario for a Business Intelligence project. He uses Crystal Reports 10 with nUnit to compare the output of a report to the raw SQL data from which the report is generated.
by Eric Landes
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 26458/ 65

Introduction

Welcome to the last part of a three-part series on Test Driven Development (TDD) for Business Intelligence projects.  Specifically, I’m writing about TDD in .NET using Crystal .NET version 10 as the Business Intelligence tool. 

In the first part of this series, I showed how I start a Business Intelligence project using C#, Crystal .NET, and nUnit.   This is done in small steps.  First, we created a simple test to load the report.  Next, we created methods and tests for logging onto the database for the Crystal Report object.

In the second part of this series, I showed how to write a test comparing the data from the report output to the data from a straight SQL query. 

In this, the last part of the series, we finish the test by coding to the scenario given to us.  Once we’re done with this test, the report is ready to be rolled into an application, and the unit tests are always there should we need to make changes.


View Entire Article

User Comments

No comments posted yet.




Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2017 ASPAlliance.com  |  Page Processed at 2017-09-21 4:31:04 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search