Tommy Juhnke dreadwarrior

Test Doubles

There are five types:

Dummy
Stub
Spy
Mock
Fake

Currently, there is an explosion of tools that aim to manage secrets for automated, cloud native infrastructure management. Daniel Somerfield did some work classifying the various approaches, but (as far as I know) no one has made a recent effort to summarize the various tools.

This is an attempt to give a quick overview of what can be found out there. The list is alphabetical. There will be tools that are missing, and some of the facts might be wrong--I welcome your corrections. For the purpose, I can be reached via @maxvt on Twitter, or just leave me a comment here.

There is a companion feature matrix of various tools. Comments are welcome in the same manner.

Create and publish a node package.

…or actually…

__How to create and publish a node package using JSHint and JSCS for linting, Mocha for testing, Istanbul for code coverage,

HTTP Streaming (or Chunked vs Store & Forward)

The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.

However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on

Modified Preorder Tree Traversal

Hierarchical data metrics that allows fast read operations on tree like structures.

Based on Left and Right fields that are set during tree traversal. When entered into node value is set to it's Left, when exiting node value is set to it's Right.

Sample implementation

	//usr/bin/env jbang "$0" "$@" ; exit $?

	//DEPS io.smallrye.reactive:smallrye-mutiny-vertx-web-client:1.1.0
	//DEPS io.smallrye.reactive:mutiny:0.7.0
	//DEPS org.slf4j:slf4j-nop:1.7.30

	package io.vertx.mutiny.pagination;

	import io.smallrye.mutiny.Multi;
	import io.smallrye.mutiny.Uni;

	package com.boohoo.esbdefused.metrics;

	import java.util.Arrays;
	import java.util.concurrent.TimeUnit;

	import com.codahale.metrics.Counter;
	import com.codahale.metrics.Gauge;
	import com.codahale.metrics.Histogram;
	import com.codahale.metrics.Meter;
	import com.codahale.metrics.MetricRegistry;

	<?php
	// Context: I'm trying to argue that DI (and DIC) are great, and DIC libs suck.
	// Happy to be proven wrong!

	final class Router {
	private $dependencies;
	public function __construct (Dependencies $dependencies) {
	$this->dependencies = $dependencies;
	// You might say that this is Service Locator, but it's not. This router is toplevel,
	// and toplevel must have access to dependencies. After that it can all just bubble nicely using proper DI.

	FROM ubuntu:16.04

	RUN PACKAGES="\
	php-cli \
	php-mysql \
	php-intl \
	php-xml \
	php-curl \
	php-dom \
	" && \

	node {
	echo 'Results included as an inline comment exactly how they are returned as of Jenkins 2.121, with $BUILD_NUMBER = 1'
	echo 'No quotes, pipeline command in single quotes'
	sh 'echo $BUILD_NUMBER' // 1
	echo 'Double quotes are silently dropped'
	sh 'echo "$BUILD_NUMBER"' // 1
	echo 'Even escaped with a single backslash they are dropped'
	sh 'echo \"$BUILD_NUMBER\"' // 1
	echo 'Using two backslashes, the quotes are preserved'
	sh 'echo \\"$BUILD_NUMBER\\"' // "1"