In a previous post we learned how to use a
together block to keep elements together. We can also layout elements in a different way: using hidden lines. We define our elements and by using the keyword
[hidden] in our line definition the elements are layout as if there was a line, but we don’t see it. This gives us great flexibility on how we layout our elements.
We have a lot of ways to customize our PlantUML diagrams. We can change the colors and we can even set gradients as color. A gradient has two colors and a direction. The direction of the gradient is set by the separator between the two colors. We can use the following separators to set the gradient direction:
/: direction top left to bottom right
\: direction bottom left to top right
|: direction left to right
-: direction top to bottom
PlantUML has some features that come from the underlying software to create diagrams. Graphviz is used by PlantUML and we can use Graphviz features in our PlantUML diagrams. For example we can align multi-line text of labels to be either center (default), left or right aligned using a Graphviz feature. When we want to text to be center aligned we simply use the new-line character
\n. If we want to have our text left aligned we use
\l instead of
\n. And to right align the text we use
Normally if we type an URL in Asciidoctor that starts with a scheme Asciidoctor knows about, the URL is turned into a hyperlink. The following schemes are recognized by Asciidoctor:
If we want to keep our URL as text and not a link we must prepend our URL with a backslash (
\). This way Asciidoctor will not transform the URL to a hyperlink in our output.
In the following example we have URL that is transformed to a link, followed by the same URL but with a backslash (
\) before it, that is not transformed:
== URL not as a link
The URL http://ift.tt/2i6Rp1o should
be turned into a hyperlink.
But now the URL \http://ift.tt/2i6Rp1o should
just be text and not a hyperlink.
If we transform our document to HTML with Asciidoctor we get the following result:
Written with Asciidoctor 18.104.22.168.
With Asciidoctor markup we can position images in our document. We can even float images, so text can next to an image, inside only below or about the image. We can also define multiple images to float, so the images are displayed on the same line next to each other. Any text that follows these images is also displayed next to the images. If we want only to have floating images, but the text starting under the images we can place the images inside an open block and assign the block the role
In a previous post we learned how to use data in CSV and DSV format. Recently we can also include tab separated values (TSV) in a Asciidoctor table. We must set the table attribute
format to the value
tsv. The data can be inside the document, but also defined in an external file which we add with the
When we write a list in Asciidoctor we can simply create a list item by starting the line with a dot (
.). To create a another list item we simply start a new line with a dot (
.). But what if we want to add a list item with multiple paragraphs, or text and a source code block element. We can use the list item continuation (
+) to indicate to Asciidoctor we want to keep these together for a single list item.
Writing a parameterized specification in Spock is easy. We need to add the
where: block and use data providers to specify different values. For each set of values from the data providers our specifications is run, so we can test for example very effectively multiple input arguments for a method and the expected outcome. A data provider can be anything that implements the
Iterable interface. Spock also adds support for a data table. In the data table we define columns for each variable and in the rows values for each variable. Since Spock 1.1 we can reuse the value of the variables inside the data provider or data table. The value of the variable can only be reused in variables that are defined after the variable we want to reuse is defined.
We all know writing tests or specifications with Spock is fun. We can run our specifications and when one of our assertions in a feature method invalid, the feature method is marked as failed. If we have more than one assertion in our feature method, only the first assertion that fails is returned as an error. Any other assertion after a failing assertion are not checked. To let Spock execute all assertions and return all failing assertions at once we must use the
verifyAll method. We pass a closure with all our assertions to the method. All assertions will be checked when use the
verifyAll and if one or more of the assertions is invalid the feature method will fail.
Writing unit tests for our handlers in Ratpack is easy with
RequestFixture. We invoke the
handle method and use a
Chain we want to test as argument. We can provide extra details on the fixture instance with a second argument, for example adding objects to the registry or setting the request method. The
handle method returns a
HandlingResult object. This object has the method
exception that we can use to see if an exception occurred in our code under test. The method throws a
HandlerExceptionNotThrownException if the expected exception doesn’t occurr.