Data Driven Projects, Tests & Frameworks

Hi Mike,

The problem that I have is that each iteration must use the same row from every sheet and every application tab.

You can do this with TestComplete, but you'll have to control the iteration yourself. I'd suggest that you create a driver for each tab and iterate through them manually, that is, something like this --

While Not Driver1.EOF

   ' Do Something

  Driver1.Next

  Driver2.Next

  ...

  Driver6.Next

WEnd

If you are using keyword tests and the Data-Driven Loop operation, you need to create and control Driver2..Driver6, as driver 1 will be controlled by the operation. To call the Next method, you can use the Call Object Method operation.

I'm also a little confused about the project layout and the framework of the tests themselves

According to the information you provided, I don't think you have to create several projects.

I'd suggest that you have your tests in one project. This way, it will be easier to maintain the NameMapping repository, for instance. You can create several tests, organize them into folders (or script units) for easier management, etc. You can create an individual test for each step, most likely, you will have something like this --

1: Startup - A test that will perform initialization actions.

2: TestTabs - This is the test that will

                        * Read data from worksheets in a loop

                        * For each data row, it will

                              - simulate user actions on the tabs (fill the tabs 1..6);

                              - output data to a file;

                              - Compare - Performs the needed verifications. 

                              Each of these substeps can be a script routine or keyword test.

                        * Call Next to proceed to the next data row.

3: Teardown - A test that will perform finalization actions.

You can create test items for tests 1, 2 and 3 on the Test Items page of the project editor.