You can choose to implement one or multiple test object configuration files (or none, if not needed). For example, you can define custom methods for one test object class in one test object configuration file, and custom methods for another test object in a different test object configuration file. You can also choose to define a group of custom methods for a test object class in one test object configuration file, and another group of custom methods for the same test object class in a different test object configuration file.
Each time you open UFT One, it reads all of the test object configuration files and merges the information for each test object class from the different files into a single test object class definition. This enables you to use the same test object class definitions when supporting different custom toolkits.