#Junit json compare code

For brevity, I am just showing the relevant code here. This class will be used to deserialize the JSON data. Let us start by creating a new generic class that takes 2 different underlying types - 1 for the Data and 1 for the Result class.

#Junit json compare how to

However, I could not figure out how to structure my JSON so that it could be parsed easily. We could reduce the number of parameters required to just one as it's just a single(albeit large) list of the same type. However, it becomes quite cumbersome to use with a large set of parameters.įor the Advent of Code test input, we would have to have a lot of parameters.

I found his solution to work very well for test cases with a small number of parameters. So you might be wondering that if Andrew has already written the article, why am I writing this? More importantly, why should you spend your precious time reading this? Since this article leans heavily on his approach, I recommend reading that first.Go on, I will wait. Andrew Lock has a great article which shows how to create a custom attribute to load the data from a JSON file.

First Passīoth these problems would just go away if we could load our test data from a file. For example, this is the sample input for the puzzle in the Advent Of Code 2018. The classes/methods can also become quite large if you have a lot of data. Member Data is similar to class data but uses a static property or method of a type instead of a class.Īll 3 of the above approaches have a shortcoming in that every time you want to add new data to test, you need a recompile.The downside is that you have to create a new class. It also allows you to pass non-constant data to the test. Class Data removes clutter from test files by moving the data to a separate class.It also can't be used when the data is not constant. Still, it gets unwieldy pretty quickly when you have many test cases. Inline Data is good when the method parameters are constant.There are 3 different ways to supply data to the parameterized tests. XUnit allows support for both parameterless and parameterized tests. If you're new to testing with xUnit, I suggest reading the getting started documentation.