-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update README and add documentation files
- Loading branch information
Showing
3 changed files
with
350 additions
and
98 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,159 @@ | ||
| ### Getting Started with Gradle | ||
|
|
||
| This tutorial explains the necessary steps to use jApprove in a Gradle project. | ||
|
|
||
| #### Setup | ||
|
|
||
| To use the entire functionality of jApprove, it is necessary to add the jApprove dependency and the Gradle-Plugin to your project's build.gradle. | ||
|
|
||
| ```groovy | ||
| repositories { | ||
| mavenCentral() | ||
| } | ||
| dependencies { | ||
| implementation("org.japprove:japprove-core:1.2.0") | ||
| } | ||
| ``` | ||
|
|
||
| ```groovy | ||
| buildscript { | ||
| repositories { | ||
| mavenCentral() | ||
| } | ||
| dependencies { | ||
| classpath("org.japprove:japprove-gradle-plugin:1.2.0") | ||
| } | ||
| } | ||
| apply plugin: 'differ-plugin' | ||
| apply plugin: 'approver-plugin' | ||
| ``` | ||
|
|
||
|
|
||
| #### Create a Simple Test | ||
|
|
||
| Although the main focus of jApprove is on JSON objects and API tests, this simple example should demonstrate how jApprove basically works. Therefore, a simple method that formats a list of strings is used. For each string that occurs in the list leading and trailing spaces are removed, all letters are converted to lower case and the first letter is converted to upper case. | ||
|
|
||
| ```java | ||
| public class StringFormatter { | ||
|
|
||
| public static List<String> format(List<String> strings) { | ||
| List<String> formattedStrings = new ArrayList<>(); | ||
| for (String s : strings) { | ||
| s = s.trim(); | ||
| s = s.toLowerCase(); | ||
| s = s.substring(0, 1).toUpperCase() + s.substring(1); | ||
| formattedStrings.add(s); | ||
| } | ||
| return formattedStrings; | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| Now, this method is tested by the usage of jApprove. An approval test is simply created by annotating the method under test with @ApprovalTest and pass the StringVerifier as a parameter. The actual test looks very similar to a usual JUnit test using the Arrange, Act and Assert (AAA) Pattern. The crucial difference is the final step where the verifier is called instead of asserting. The verifier reads the content of the string and compares it to a previously approved version. This version is stored in the so-called _baseline_ that can be set as a parameter of the @ApprovalTest annotation. If no parameter is set, a random name is used. Currently, this tool uses a text-based approach and therefore the baseline is just a simple text file. | ||
|
|
||
| ```java | ||
| public class StringFormatterTest { | ||
|
|
||
| @ApprovalTest(baseline = "strings") | ||
| void testFormat(StringVerifier stringVerifier) { | ||
| // arrange | ||
| List<String> names = Arrays.asList("PETER", "MiKe", "joHn", " pAuL "); | ||
|
|
||
| // act | ||
| List<String> formattedNames = StringFormatter.format(names); | ||
|
|
||
| // approve | ||
| stringVerifier.verify(formattedNames); | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| The test can be started like a usual JUnit test (e.g. by clicking a button within an IDE). Because there is no approved version, the test obviously fails the first time. As a side effect, the file _simpleSorting.txt_ has been created in the _build/baselineCandidates/_ directory. This directory is used to store all unapproved versions. To approve this version, use the following command: | ||
|
|
||
| `gradle approve --baseline=strings` | ||
|
|
||
| With the `gradle approve` command the approve function of the Gradle-Plugin is called. The --baseline option is used to specify the baseline of the respective test case. In this case `--baseline=strings`. | ||
|
|
||
| Finally, if the test is started again, it passes successfully. Meanwhile, the file _simpleSorting.txt_ has been moved from _build/baselineCandidates/_ directory to a new _baselines/_ directory where all approved versions are stored. | ||
|
|
||
| If you make some changes to the the code (e.g. refactoring, remodularization, ...), you can simply rerun the test to verify that the behaviour of the method is still the same. If there are changes, the test fails and the the error message shows the differences. At this point you are also able to approve the new version, if the changes are accepted or even desired. | ||
|
|
||
| If there are many changes or a large output, it is possible to inspect the differences with the aid of an external diff tool. This tool has to be configured in the japprove.properties file that is located in the _src/test/resources/_ directory. For example, the properties file could look like the following one: | ||
|
|
||
| ``` | ||
| diffTool=C:/Program Files/KDiff3/kdiff3.exe diff | ||
| ``` | ||
|
|
||
| To call this tool, use the following command: | ||
|
|
||
| `gradle diff --baseline=strings` | ||
|
|
||
|
|
||
| #### Create a Test for a JSON Object | ||
|
|
||
| The test of JSON objects is very similar to the test of strings. But nevertheless, there are a few differences. To demonstrate them, a simple method that returns a simple mock state is used. The state is returned as JsonNode and consists of the actual state and a simple timestamp. | ||
|
|
||
| ```java | ||
| public class SimpleState { | ||
|
|
||
| public static JsonNode getState() { | ||
| String json = "{\"state\" : \"OK\"," + "\"timestamp\" : \"1579622991\"}"; | ||
| ObjectMapper objectMapper = new ObjectMapper(); | ||
| JsonNode jsonNode = null; | ||
| try { | ||
| jsonNode = objectMapper.readTree(json); | ||
| } catch (JsonProcessingException e) { | ||
| e.printStackTrace(); | ||
| } | ||
| return jsonNode; | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| To create an Approval Test for this state, it is necessary to pass a JsonVerifier instead of a StringVerifier. The JsonVerifier is designed for JsonObjects and consists of a separate implementation. That means, for example, the order of the nodes does not matter and the test passes even if you change the order. Furthermore, it enables to ignore elements of the JSON object. For example a timestamp that is different every time the test is started can simply be excluded from the test by the usage of the ignore method. | ||
|
|
||
| ```java | ||
| public class SimpleStateTest { | ||
|
|
||
| @ApprovalTest(baseline = "json") | ||
| public void testGetState(JsonVerifier jsonVerifier) { | ||
| JsonNode state = SimpleState.getState(); | ||
| jsonVerifier.ignore("timestamp").verify(state); | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| The usage of the JsonVerifier also enables testing REST APIs in the case they return JSON objects. | ||
|
|
||
|
|
||
| #### Customize jApprove properties (optional): | ||
|
|
||
| By default the the approved files are stored in a _baselines/_ directory and the unapproved files in a _build/baselineCandidates/_ directory. If other locations are desired, they can be changed in the japprove.properties file in the _src/test/resources/_ directory. For example, the properties file could look like the following one: | ||
|
|
||
| ``` | ||
| baselineDirectory=approvedFiles | ||
| baselineCandidateDirectory=build\\unapprovedFiles | ||
| ``` | ||
|
|
||
|
|
||
| #### Basic Commands | ||
|
|
||
| * Approve a failing test with the following command: | ||
|
|
||
| `gradle approve --baseline=${testname}` | ||
|
|
||
| * Approve the changes of all failing test at once with the following command: | ||
|
|
||
| `gradle approve --all` | ||
|
|
||
| * Start a batch process and approve/diff all failing tests step by step with the following command: | ||
|
|
||
| `gradle approve` | ||
|
|
||
| * Highlight the differences within an external diff tool with the following command: | ||
|
|
||
| `gradle diff --baseline=${testname}` | ||
|
|
||
|
|
||
|
|
Oops, something went wrong.