In this post, I’ll briefly describe the features and uses of Tidbit, and walk you through some simple use cases. Tidbit is a simple tool to populate your Sugar instance with large amounts of data for load testing purposes.
Using a few short command line options, you can generate records with Tidbit for various Sugar modules. Using only the load command line argument, Tidbit will create that many Accounts, and records for other modules according to the ratios defined in the install_config.php file. Here’s a short example:
php install_cli.php -l 100 -o
The output from Tidbit tells you what’s being created:
If you want more fine-grained control over the ratio of records created, you can edit install_config.php to suit your needs. This file contains an array called $modules, where the module names are mapped to integer values.
If you are running a Sugar installation featuring modules built using Module builder or edited using Studio, Tidbit can create records for these modules as well. If you give the –allmodules command line argument, Tidbit automatically detects all modules and creates records for them. If any module has customized fields from Studio, Tidbit will detect these changes and generate the appropriate type of data for the field.
I also want to mention one more feature that helps to populate the Sugar installation with a “realistic” data set. If you use the –allrelationships command line argument, Tidbit detects any custom relationships created using Studio and relates the records it creates according to what it finds.
Tidbit has been around for a while so I’m sure many are already familiar with it. Still, I hope this post can serve as a reminder and inform you of recently added features.
Check out Tidbit here.