Grouper Developers Forum

[Chris Hyzer <>]

Hmmm, I think hooks are added at startup, and if you want to change them you have to bounce.

 

So a unit test to test how hooks are read from the config file, would need:

 

1.       Edit GrouperHookType, add a public static method called clearConfiguredHooksForTesting() to set hookTypes to null

2.       In your test, call that method at the beginning of the test and in a finally block (to reset stuff for other tests)

3.       Add your config overrides like this:

     

GrouperConfig.retrieveConfig().propertiesOverrideMap().put(“key”, “value”);

 

4.       Then call the method that would use the hook, it should work.  The override gets cleared in GrouperTest so don’t worry about clearing it, though you could if you like:

 

GrouperConfig.retrieveConfig().propertiesOverrideMap().clear();

 

Let me know if you need more help J

 

Thanks

Chris

 

 

From: [mailto:] On Behalf Of John Gasper
Sent: Sunday, May 24, 2015 6:17 PM
To:
Subject: [grouper-dev] Running Grouper Unit Test

 

So I’m working on https://bugs.internet2.edu/jira/browse/GRP-1139 and like to form some unit test around validating that multiple hook classes are read in through the grouperClient config that gsh uses.

 

I’ve found some config test for the cascading properties and think I have a valid test related to the issue, but I’m not sure of the best practice way of executing it? Is there a standard method for doing the compile and test execution related to the Grouper Client that I’m missing?

 

Thanks,

John

 

-- 

John Gasper
IAM Consultant
Unicon, Inc.
PGP/GPG Key: 0xbafee3ef