codification

FROM node

EXPOSE 9615

RUN mkdir -p /src/app
COPY server.js /src/app/

WORKDIR /src/app

CMD node server.js

codification

(set-env!
 :source-paths #{"src/clj"}
 :resource-paths #{"resources"}

 :dependencies '[[org.clojure/clojure "1.9.0-alpha14"]
                 [amazonica "0.3.78"]])

codification

version: "2"
services:
    rsyslog:
        image: jumanjiman/rsyslog
    proxy:
        image: haproxy
        volumes:
            - ./:/cfg
        volumes_from:
            - rsyslog

codification

! Xft settings ---------------------------------------------------------------

Xft.dpi:        96
Xft.antialias:  true
Xft.rgba:       rgb
Xft.hinting:    true
Xft.hintstyle:  hintslight

! URxvt settings ---------------------------------------------------------------
!URxvt*font: 				xft:Anonymous Pro:pixelsize=12:antialiasing=true

codification

So.
First there was this, from @jbrains:
https://twitter.com/jbrains/status/868129015986618368

> There is more to #tdd than just writing the test first and looking
> for mistakes in the runtime behavior of the system.

Then there was this response from @gdinwiddie:
https://twitter.com/gdinwiddie/status/868279210963587073
> Yeah, but that's a good first step toward learning TDD.

codification

package tst;

import org.junit.Test;
import org.openqa.selenium.By;
import org.openqa.selenium.NoSuchElementException;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.openqa.selenium.support.ui.FluentWait;
import org.openqa.selenium.support.ui.Wait;

codification

import org.junit.jupiter.api.Assertions;

public class FirstTest extends FuncTest {

    {{
        describe("A test", () -> {
            Assertions.assertTrue(() -> true);
        });

        describe("Another test", () -> {