Java Faker VS restassured-complete-basic-example

JavaFaker for generating random data https://github.com/DiUS/java-faker

I've been using https://github.com/DiUS/java-faker which seems to be much more popular. How is this one different?

This has another bottleneck, each time you request something, it ends up with a IO call to open a file, as all fake data is stored in a file: https://github.com/datafaker-net/datafaker/blob/master/src/main/resources/en/dragon_ball.yml I recently filed a bug to javafaker that in some cases file descriptor was never closed, resulting in even worse performance and memory leaks, killing our service after millions of method calls.

[]JavaFaker](https://github.com/DiUS/java-faker) is an open-source library based on Faker to generate fake data.

For that I will introduce you JavaFaker, a is a library that can generate fake random data every time it’s called. For example: if you generate a name all the names generated will be different.

The restassured-complete-basic-example project has a factory data class to generate all the necessary data in different conditions. It’s a good real-world example.

In my restassured-complete-basic-example project you can found:

In the base test class

In the custom message format class

In the initial state specs

The configuration file

In some cases, you can even call some existing endpoints to provide data you need to use in your tests. It’s the case for the method getAllSimulationsFromApi() where I’m getting the existing simulation, using it in the oneExistingSimulation() factory method to get a random existing simulation and on allExistingSimulations() to return all the existing simulations.

In the project restassured-complete-basic-example you will find different data generation approaches in the data package. The SimulationDataFactory class has a complete set of factory methods for all the possible scenarios.