| 1 |
The write-test-dbs script will create a small set of test databases with a |
| 2 |
variety of data and record sizes (24, 28, & 32 bit). |
| 3 |
|
| 4 |
These test databases are useful for testing code that reads MaxMind DB files. |
| 5 |
|
| 6 |
There is also a `maps-with-pointers.raw` file. This contains the raw output of |
| 7 |
the MaxMind::DB::Writer::Serializer module, when given a series of maps which |
| 8 |
share some keys and values. It is used to test that decoder code can handle |
| 9 |
pointers to map keys and values, as well as to the whole map. |
| 10 |
|
| 11 |
There are several ways to figure out what IP addresses are actually in the |
| 12 |
test databases. You can take a look at the |
| 13 |
[source-data directory](https://github.com/maxmind/MaxMind-DB/tree/master/source-data) |
| 14 |
in this repository. This directory contains JSON files which are used to |
| 15 |
generate many (but not all) of the database files. |
| 16 |
|
| 17 |
You can also use the |
| 18 |
[mmdb-dump-database script](https://github.com/maxmind/MaxMind-DB-Reader-perl/blob/master/eg/mmdb-dump-database) |
| 19 |
in the |
| 20 |
[MaxMind-DB-Reader-perl repository](https://github.com/maxmind/MaxMind-DB-Reader-perl). |
| 21 |
|
| 22 |
Some databases are intentionally broken and cannot be dumped. You can look at |
| 23 |
the |
| 24 |
[script which generates these databases](https://github.com/maxmind/MaxMind-DB/blob/master/test-data/write-test-data.pl) |
| 25 |
to see what IP addresses they include, which will be necessary for those |
| 26 |
databases which cannot be dumped because they contain intentional errors. |