Unit Testing - Controller/Screen/Form consistency

[Bob Morley]

One thing that has come up is situations where we have entries in our controller that reference missing screens and/or screens that reference missing widgets (mostly forms).  What I wanted to do was create a unit tester that would walk the controller path and find missing references.

Has anyone does this before or have any thoughts?

[David E Jones-3]

On Mar 24, 2009, at 10:08 AM, Bob Morley wrote:

>
> One thing that has come up is situations where we have entries in our
> controller that reference missing screens and/or screens that  
> reference
> missing widgets (mostly forms).  What I wanted to do was create a unit
> tester that would walk the controller path and find missing  
> references.
>
> Has anyone does this before or have any thoughts?

The WebTools ArtifactInfo stuff does something like this (not sure if  
it will meet your needs). It does parse and load all of the various  
artifacts in OFBiz and in the initialization log shows warnings about  
missing things (bad references) like this.

-David

[Bob Morley]

Yes good point -- I had noticed the artifact stuff; what we were hoping for was a unit tester that would be run as part of the unit test target so that we can have a nightly report on any "bad stuff" people had checked in.

David E Jones-3 wrote

The WebTools ArtifactInfo stuff does something like this (not sure if  
it will meet your needs). It does parse and load all of the various  
artifacts in OFBiz and in the initialization log shows warnings about  
missing things (bad references) like this.

-David

[David E Jones-3]

Such a thing could certainly be written...

-David


On Mar 24, 2009, at 1:21 PM, Bob Morley wrote:

>
> Yes good point -- I had noticed the artifact stuff; what we were  
> hoping for
> was a unit tester that would be run as part of the unit test target  
> so that
> we can have a nightly report on any "bad stuff" people had checked in.
>
>
> David E Jones-3 wrote:
>>
>>
>> The WebTools ArtifactInfo stuff does something like this (not sure if
>> it will meet your needs). It does parse and load all of the various
>> artifacts in OFBiz and in the initialization log shows warnings about
>> missing things (bad references) like this.