Skip to main content

Digging IDMUnit - IdMUnit a must-have automated testing tool that integrates with Designer for Novell Identity Manager





Good news, The IDMUnit 2.0 is out (http://www.idmunit.org/web/guest/idmunit20)!.. and I just couldn't wait to try the tool and do some hands on with it. Now it comes with a documentaiton and a WebMinar which helps a lot to understand how it works and how it integerates with the Novell Designer.

The Webminar is encoded with the "G2M3" encoding, so you need a decoder in order to see both video and audio. I downloaded it from the web : https://www2.gotomeeting.com/codec




I started with installing the tool on my PC Windows Vista 32bit OS. I have the following setup:

Novell Designer Version: 3.5, Build id: 20090916
Novell Identity Manager 3.6.1 Windows Server 2003 SP3
Novell eDirectory 8.8.x

The first thing the IDMUnit documentation says to apply so called "Eclipse Overlay", i downloaded "Eclipse IDE for Java Developers (92 MB)" that from the URL "http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/galileo/SR1/eclipse-java-galileo-SR1-win32.zip"

After applying the "Eclipse Overlay" on my existing Novell Designer installation i started Novell Designer, which started normally. I imported a IDM project from a test lab into it and started created a IDMUnit project by going through "Windows/Open Perspective/Java".

Created a Java project with following folder structure:

the idm-runtime must be in your classpath and all the required libs.

under the src directory, i have my testJava classes and the .xls excel workbook (testCases) into it.

Under IdMUnitProperties folder i have "idmunit-defaults.properties" file and log4J configuration files.

Under IDMUnitProfiles folder i have the "idmunit-config.xml" profile file which has the connection information for different sources like AD , LDAP and SQL etc.

Remember in order to store password into the profile file you need to use EncTool which comes with the IDMUnit runtime. I executed the tool from Netbeans by doing:

org.idmunit.EncTool encTool = new org.idmunit.EncTool("IDMUNIT1") ;
System.out.println(encTool.encryptCredentials("myPasswordString"));



The folder "IDMUnitProperties" is in my Build Path, and the file "idmunit-defaults.properties" in this folder has following content:

ConfigLocation=./IDMUnitProfiles/idmunit-config.xml
ApplySubstitutionsToOperations=true
ApplySubstitutionsToData=true

After settingup the project, you are just ready defining your testCases in the .xls files. The .xls file name should be the same as your java testClass name.

and the finally creating some testCases, i tried my tests using IDMUnit, and it worked superbly by failing the tests first!

TDD (test driver design principals)

1. Add a test

2. Run all tests and see if the new one fails

3. Write some code


4. Run the automated tests and see them succeed

5. Refactor code





finally after doing some trials, i managed to run the IDMUnit with Novell Deisnger, and now my test bar is green!

"Keep the bar green to keep the solution clean"


Labels:

Comments

Isabelle Andrade said…
Hello.

Great post. I have a question though.
How did you apply the eclipse overlay to Designer 3.5? The IdMUnit documentation specifies that the Designer/eclipse dir should be substituted by the new eclipse overlay, but Designer 3.5 does not have an specific eclipse dir.

Anyway, thanks for your help!
November 9, 2012 at 1:17 PM
Post a Comment

Popular posts from this blog

NetIQ IDM - SOAP driver -- Handling SOAP service response and manufacturing user association without XSLT

Always pain working with SOAP service and its handling of service response on Query(matching) for user to work with matching policies? Here is the quick wins; without reading  those long lengthy & boring useless SOAP driver blog series at netIQ forums; 1. Make sure you have mapped User class in the schema map with some service attributes 2. Make sure Input and Output policy is registered with all the namespaces you have in your request/response soap messages, example <policy xmlns:soap="http://www.w3.org/2003/05/soap-envelope" 3. I have added operation-data (which is being generated from the Output policy) as part of the SOAP query, but you can skip it if you do not need this. src-dn and association are important to indicate engine for building association.  Operation data will help you to identify operation type and you can carry actions according to it. Inject this on Output ( To support user matching) to send service request: < rule > ...
1 comment
Read more

NetIQ IDM - Adding operation-data to subscriber command transformaiton custom commands

Recently i had to execute EOL cmdlets using psexecute though new NetIQ azure ad driver, since this operation is fire and forget in nature, i would like to track whole request and response for my own generated commands from subscriber command transofrmaiton policy, so i solved it by following policy: < do-set-dest-attr-value direct = "true" name = "psexecute" > < arg-association > < token-resolve datastore = "src" > < arg-dn > < token-text xml:space = "preserve" > {userref} </ token-text > </ arg-dn > </ token-resolve > </ arg-association > < arg-value type = "string" > < token-local-variable name = "cmdlet" /> </ arg-value > </ do-set-dest-attr-value > < do-append-xml-element expression = "../modify[@direct]" na...
2 comments
Read more

Getting into Microsoft Identity Manager ...

Hmm... Microsoft Identity Manager 2010 is out.. but i really wanted to see how the new version is better then its older versions... i have read lots of documentation about FIM2010 and its declarative programming capabilities, MPRs (Management policy rules), workflows, Sets, Group etc, so before touching the fancy parts, i decided to dig into first how the sync-engine or as it previously called MIIS works before doing hands-on with the fancy FIM2010 and the sharepoint based user portal.. Going back to its earlier version and doing hands-on was necessary for me, since FIM2010 documentation always referred the "Classic-rules" as the more powerful then the declarative rules/programming in FIM2010. So i wanted to experience the power into Microsoft IdM before touching the declarative programming(less-power'd) stuff in FIM2010. Having already worked with event-based IdM products such as nOvell identity manager, i was excited to work with the state-based systems such as FIM2010....
Post a Comment
Read more