An early decision I had to make was whether I should programmatically determine which reports were available to test and programmatically determine which of their parameters were required, etc… or if I should track my own expectations for the reports I expected and the parameters owned by each. I went with the later because I don’t trust the devs to keep the former stable. JART needs the ability to determine when the wrong reports get released; a common dev mistake.

Since I have about 150 distinct reports, each with their own combinations of shared filter controls and possible filter values, I made a matrix in MS Excel. The matrix rows represent each report, the columns represent each filter control, and the intersections are the filter values I use to pass into JART for each report’s filter criteria controls. This single spreadsheet controls all the tests JART will execute.

Another advantage, for me, to controlling the tests via an Excel spreadsheet is that my BL already maintains an Excel spreadsheet that specifies which of the 150 reports should be available in each build. The BL’s list can control which reports JART tests, just like the BL's list controlled which reports I tested.

JART simply loops through each report in said matrix and provides standard verifications for each. Verifications are important, and tricky for report AUTs, so I’ll save those for the next post.


  1. crayexterminaton said...

    that cockroach is disturbing. and I also find it disturbing that you don't find it disturbing.

    how long did it take to put the "finishing touch" on that one?

  2. Alex said...

    Whee! Can I get the code? I promise to share with you some of the cool stuff we're doing!

  3. Eric Jacobson said...


    How long for what?

    The framework, so far about 8 hours of work. The JART logo, about 30 hours.

    In all seriousness, the cockroach, as seen in my TestThisBlog header, was found dead on my dining room floor. I snapped the photo of it flipped over, just like it appears now. When I first moved to Georgia I found these bugs disgusting. But now that I've tested your code, I realize there are far larger bugs to worry about.

  4. Eric Jacobson said...


    Sure, I'll send it to you. But only if you promise to post about how great of a coder I am and how you want to buy a JART t-shirt.

    ...or maybe you can write my some QTP code to interact with those damn Synfusion grids my devs keep using.

Copyright 2006| Blogger Templates by GeckoandFly modified and converted to Blogger Beta by Blogcrowds.
No part of the content or the blog may be reproduced without prior written permission.