Library to build your POJO entities using a very intuitive DSL.
NOTE: from version 0.2.0 the DSL has changed a little bit to provide more support and new features. you will have to update your test in order to use the new version but hopefully the DSL won't change from now onwards.
Most of the time when I am writing my tests I have the need to write clean and readable tests. One way to achieve is by having Test Builder, but normally it takes time and are difficult to mantain in time. So after looking around I came up with this library to help you to create your pojo in a different and easy way.
There are several ways to use it but the most flexible for me is creating a Class Builder that contains all the logic to create the objects. The same example you can find in the lib tests.
you can inspect this demo project to see how to use this library.
public class PojoBuilder {
public static Field<String> name = new Field<>();
public static Field<String> value = new Field<>();
public static Field<String> name2 = new Field<>("defaultName");
public static Field<String> value2 = new Field<>("defaultValue");
public static Function<LookUp, Pojo> creator = lookUp -> new Pojo(lookUp.get(name, "defaultName"),
lookUp.get(value, "defaultValue"));
public static Function<LookUp, Pojo> creatorWithPredefinedDefaults = lookUp -> new Pojo(lookUp.get(name2),
lookUp.get(value2));
}There many things going on there but I will try to explain it in the best way that I can. There are s few concepts to keep in mind; Field, Creator and LookUp.
The Creator is just a java Function that receives as Argument a LookUp and return the object. NOTE: Since version 0.2.1 the Creator interface was removed in order to use a Function.
The Field represent the value that you want to change by using the DSL in the construction of your objects.
In charge of binding the Field instance and getting the corresponding value in the creator class. In the example above the Creator is building a pojo using the constructor method and it is using the lookUp instance to get the corresponding value.
public static Field<String> name = new Field<>();
public static Field<String> value = new Field<>();
new Pojo(lookUp.get(name, "defaultName"),
lookUp.get(value, "defaultValue")the lookUp method is using a Field instance as first parameter and the second parameter to define what the default value will be in case that we don't set it by the DSL. The other way to set the default value is by setting at the construction of the field it self so at the lookUp level you don't have to pass it.
public static Field<String> name2 = new Field<>("defaultName");
public static Field<String> value2 = new Field<>("defaultValue");
new Pojo(lookUp.get(name2),
lookUp.get(value2));and below is the code to generate your pojo.
Pojo pojo = Builder.build()
.entity(PojoBuilder.creator)
.applyValue(PojoBuilder.name, "nameoverrideed")
.applyValue(PojoBuilder.value, "valueoverrided")
.get();You can nullify a field by just using nullify Method from DSL.
Pojo pojo = Builder.build()
.entity(PojoBuilder.creator)
.applyValue(PojoBuilder.name, "nameoverrideed")
.nullify(PojoBuilder.value)
.get();If you already have creators and you want to reuse them on other creator, you can achieve it by:
- Setting your existing creator as a default value when you define your new creator. Note that you can even override the values of the creator that you are using as default.
public static Field<String> name = new Field<>();
public static Function<LookUp, String> nameCreator = lookUp -> lookUp.get(name, "test1");
public static Field<String> secondName = new Field<>();
public static Function<LookUp, String> creator = lookUp -> lookUp.get(secondName, secondCreator);
Pojo pojo = Builder.build()
.entity(creator)
.applyValue(name, "test2")
.get();- The other way is by overriding a field using a creator or Supplier as value:
public static Field<String> secondName = new Field<>();
public static Function<LookUp, String> secondCreator = lookUp -> lookUp.get(secondName, "test1");
Pojo pojo = Builder.build()
.entity(PojoBuilder.creator)
.applyValue(PojoBuilder.name, "nameoverrideed")
.applySupplier(PojoBuilder.secondName, () -> "secondName")
.applyCreator(PojoBuilder.value, secondCreator)
.get();- You can also from there override a field of secondCreator but you have to override those before using the secondCreator.
As easy as is creating an entity with Builder4Test, just use list method from the DSL and add as many elements to the collection as you want. For each element you can override all the fields. In the example below we are creating a list of two elements overriding the fiend name.
List<Pojo> testSiumple = Builder.build()
.list(creator).elements()
.element()
.applyValue(name, "testSiumple")
.end()
.element()
.applyValue(name, "testSiumple2")
.end()
.get();Also if you want to generate a certain amount of elements using the defaults values or random now it is supported.
List<Pojo> testSimple = Builder.build()
.list(creator)
.size(5)
.applySupplier(name, () -> RDG.string())
.applySupplier(value, () -> RDG.string())
.get();This code will generate a List of five elements and each element will contain a random value and field. Using defaults generator provided by Fyodor is easy to generate your random values.
Also if you want to generate a sequence value using index of the iteration you can supply a Function
List<Pojo> testSimple = Builder.build()
.list(creator)
.size(5)
.applySequence(name, (index) -> index+ "test")
.get();This will generate a list of Pojo with name 1test, 2test, 3test...
- generate a list from a range is also possible:
List<Pojo> testSimple = Builder.build()
.list(creator)
.range(1, 5)
.applySequence(name, (index) -> index+ "test")
.get();Note: that you can use creators as default values in your collections.
The library is highly inspired by
Make it Easy And AssertJ
Make It Ease lib provides a Hamcrest style DSL but I am more fun of using a builder kind of DSL like AssertJ that offers straight away the option that I can use. I want to say thank you to all the collaborator of MakeItEasy project.