Focal Point
Unit testing in WebFocus

This topic can be found at:
https://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/6381073551

February 21, 2006, 12:40 PM
Celestun
Unit testing in WebFocus
As I understand the term, *unit testing* is an object oriented methodology for incremental testing of components. The test design and data is developed for every incremental function *prior* to coding.

All the examples I have seen appear to be for transaction processing activites.

Does anyone have an adaptation of Unit Testing for WebFocus reporting?

Any ideas?
February 21, 2006, 03:42 PM
Prarie
Are you upgrading to a new version or implementing WebFocus replacing something else?


In Focus since 1993. WebFOCUS 7.7.03 Win 2003
February 21, 2006, 05:33 PM
Celestun
My concern is about a unit testing paradigm for WebFocus reporting.

It is NOT about installing or upgrading.
February 22, 2006, 08:58 PM
Piipster
I don't think this will quite answer your question, but these are things I think about when testing a report to confirm that my results are correct:

How specific are your report specs?

Do you have a test environment that will provide you reproducible results so that you can continually retest reports after changes?

Can you identify a simple population to verify complex calculations? In the report specs, how do you identify specific data elements that are required? Specific calculations?

Identify ALL possible combinations of data that need to be tested.

How do you verify your results ... dump the source data of a small population that covers the different combinations and verify everything manually? Compare to existing reports that you assume are correct?

Just some ideas.... I hope they help.


ttfn, kp


Access to most releases from R52x, on multiple platforms.
February 24, 2006, 09:14 AM
EJL
"Unit Testing" as an IT term isn't really related to object oriented development. (although there may be a framework out there somewhere that formally uses that name). Unit testing is just testing individual components and has been around for some time.

What you describe sounds to me like "Test Driven Development" or "Test First Design". I don't see much of an opportunity for that approach in WebFocus development but I'm not an expert in the area. You could use a tool to automate your calling of the report and to check the HTML sent back at the field level but that's just basic stuff and I would think hardly qualifies as more than just a solid approach to testing.