Automated FIM Testing

Automated testing of FIM has three primary benefits for the organization.

  1. It reduces development costs by shortening the project
  2. It reduces risk through improved change control
  3. It improves project outcomes by verifying business requirements

Reducing Costs

Automated testing reduces costs by dramatically reducing the time needed to develop and test solutions.

The majority of any FIM 2010 project is spent in debugging, and QA testing. The majority of testing is spent setting up data and waiting for synchronizations to run. FIM Test reduces the time spent to set up data for tests by connecting directly to systems that feed into FIM and loading and manipulating preconfigured data. Essentially, instead of manually entering data for every test, you enter once in your FIM Test configuration then re-use it as many times as needed.

FIM Test dramatically reduces time spent waiting for synchronizations because runs management agents and programs in the context of test cases. When testing with small numbers of objects (like in most development testing scenarios), most of the time spent in synchronization is either tedious GUI manipulation, or dead time waiting for the Synchronization Service Manager to refresh. FIM Test is often able to run dozens of synchronizations in the time it would take to an operator do do one or two manual runs.

Reducing Risk

FIM 2010 has a somewhat unique risk profile. The batch nature of FIM means that it’s less sensitive to downtime than other critical tools. However its usual role of managing user accounts means that a configuration error can have devastating effects on the enterprise. Most seasoned FIM professionals have horror stories of events like enterprise wide password resets or account deletions.

Automated testing controls risk by allowing efficient verification of existing functionality. FIM Test provides the ability to run tests and automatically verify the results in target systems. This allows effective QA regression testing without imposing unrealistic burdens on project timelines.

Verifying Business Objectives

Often when deploying FIM 2010, it can be challenging to verify that adequate tests have been performed to provide coverage of all business requirements and objectives. FIM Test allows testers to create a mapping from business objectives to test cases.

With FIM Test it is possible to generate reports illustrating how objectives and requirements have been mapped to automated tests. FIM Test cases are repeatable and make verifiable assertions about how FIM 2010 changes target systems, so it is easy to demonstrate the results of a particular business objective on an as-needed basis.

Test results based on business objectives are a valuable deliverable that allows businesses to be more confident about implemented functionality before signing off on deployment.

Copyright © SoftwareIDM

Table of Contents