There are free on-line tools for JSON file creation. We have at least 20 reasons to use DTM Data Generator for JSON instead. There are most important of them:
| Option | DTM Data Generator for JSON | On-line generators |
|---|---|---|
| JSON file structure import | Yes | No |
| A lot of file generation per run | Yes | No |
| Project file sharing to team | Yes | No |
| Version control systems compatibility | Yes | No |
| User's text file as a source | Yes | No |
| User's Excel spreadsheet as a source | Yes | No |
| Local or remote database table or query as a source | Yes | No |
| XML document as a source | Yes | No |
| Extended database system integration | Yes | No |
| Built-in expression engine for better test data creation | Yes | Limited |
| Value-to-value dependencies like (if A>5 use B=1024) | Yes | Limited |
| Process automation and scheduling | Yes | No |
| Value by example feature support | Yes | No |
| Built-in sets of well known data: counties, cities, currencies, streets, names, etc. | Yes | Limited |
| Formating options for numbers, dates, time values, etc | Yes | Limited |
| Group of data and value repeating feature | Yes | Limited |
| Custom and external value generators | Yes | No |
| Node probability feature support | Yes | No |
| Can populate test MongoDB database | Yes, with Data Loader | No |
| Can populate test CouchDB database | Yes, with Data Loader | No |
| Can populate test RavenDB database | Yes, with Data Loader | No |
| $DATE$ and $TIME$ macro support for unique file name generation | Yes | No |
| Fast and professional technical support | Yes | Limited |