Current default properties are either generated based on handler rules or supplied by TestDataConfig.
As part of the refactor for 3.3, the groundwork is in place to allow for pluggable property resolvers to allow for more flexibility.
TestDataConfig would just be one of several property resolvers.
Another resolver could use the Faker library to generate more realistic fake data.
One design goal would be to instantiate a single resolver context so that resolvers could carry state to more efficiently create sequential data, unique data, etc.
Current default properties are either generated based on handler rules or supplied by TestDataConfig.
As part of the refactor for 3.3, the groundwork is in place to allow for pluggable property resolvers to allow for more flexibility.
TestDataConfig would just be one of several property resolvers.
Another resolver could use the Faker library to generate more realistic fake data.
One design goal would be to instantiate a single resolver context so that resolvers could carry state to more efficiently create sequential data, unique data, etc.