The purpose of this paper is to describe general data warehouse structure and background, as well as specific situations encountered during the testing effort for our project. Our project was to test a data warehouse and data mart for a large research department of a pharmaceutical manufacturing company. This was a pilot project and our efforts, if successful, would pave the way for
future data warehouse projects within the company.
Our role on the project team was to provide quality through validation of the business rules. We met this challenge by determining if the extract/transform/load (ETL) process was functioning in the approved manner. We created basic principles that were used as a starting block
for our process.

While Web-based GUI testing is all the rage, lots of us still operate in a world of UNIX shells, command lines, and scripts. Automated testing in this world traditionally consists of executing the command being tested, then running a series of additional commands that perform validation. But how do you automate the test when the command being run expects answers? The solution: an Intelligent, Interactive Testing Tool (IITT). An IITT requires no scripting to write or maintain as it's completely data driven, meaning non-programming folks can create and maintain their own automated tests. This presentation demonstrates the ease with which an automated test can be developed using IITT's logic for non-GUI interactive applications.

Basis path testing is a structural testing technique that identifies test cases based on the flows or logical paths that can be taken through the software. A basis path is a unique path through the software where no iterations are allowed; they're atomic level paths, and all possible paths through the system are linear combinations of them. Basis path testing uses a Cyclomatic metric that measures the complexity of a source code unit by examining the control flow structure. Basis path testing can also be applied to integration testing when software units/components are integrated together. You'll see how the use of the technique quantifies the integration effort involved as well as the design-level complexity.

While revenues, cash flow, and earnings are vital statistics of a company's well-being, they're the by-product of what the company actually offers up as a product or service. Therefore, if the offering doesn't produce ROI for the customer, it doesn't represent a viable business opportunity. In this session, take a look at testing from the perspective that it's a service provided to your company. Since testing impacts not only your company, but also your company's customers, then you, as a tester, must provide and prove ROI to succeed in a business environment. Having the ability to discuss, define, manage, and demonstrate the ROI of testing is an invaluable skill. This session gives you the information and tools you need to define and demonstrate models of testing ROI, then translate them into upper management's terms.