aterreno

Idiomatic React Testing Patterns

Testing React components seems simple at first. Then you need to test something that isn't a pure interaction and things seem to break down. These 4 patterns should help you write readable, flexible tests for the type of component you are testing.

Setup

I recommend doing all setup in the most functional way possible. If you can avoid it, don't set variables in a beforeEach. This will help ensure tests are isolated and make things a bit easier to reason about. I use a pattern that gives great defaults for each test example but allows every example to override props when needed:

See https://github.com/delitescere/docker-zulu and https://github.com/delitescere/docker-lein

Here is a high level overview for what you need to do to get most of an Android environment setup and maintained.

Prerequisites (for Homebrew at a minimum, lots of other tools need these too):

XCode is installed (via the App Store)
XCode command line tools are installed (xcode-select --install will prompt up a dialog)
Java

Install Homebrew:

ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"

MIT License

Copyright (c) [year] [fullname]

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

	name: CI
	on: [push]
	jobs:
	setup:
	runs-on: ubuntu-latest
	outputs:
	test-chunks: ${{ steps['set-test-chunks'].outputs['test-chunks'] }}
	test-chunk-ids: ${{ steps['set-test-chunk-ids'].outputs['test-chunk-ids'] }}
	steps:
	- uses: actions/checkout@v2

	#!/usr/bin/env bash
	find node_modules \( -name '__tests__' -o \
	-name 'test' -o \
	-name 'tests' -o \
	-name 'powered-test' -o \
	-name 'docs' -o \
	-name 'doc' -o \
	-name '.idea' -o \
	-name '.vscode' -o \
	-name 'website' -o \

	#!/usr/bin/env bash
	#
	# The bumbailiff allows the team to take up a small amount of technical debt
	# (TODOs in the code) for a limited period. After that period the script fails.
	#
	# Originally written by Aslak Hellesoy
	#
	set -ef -o pipefail
	IFS=$'\n' # make newlines the only separator

	(ns riemann-config-test
	(:use
	midje.sweet
	riemann.streams
	riemann.client
	riemann.email
	riemann.sns
	[riemann.time :only [unix-time linear-time once! every!]])
	(:require
	riemann.streams

	//Having to include so many different header files to do basic
	//things like open a file, use strings, vectors and tuples, etc,
	//is still annoying.
	#include <fstream>
	#include <vector>
	#include <map>
	#include <tuple>
	#include <string>

	//To use C++11 lambdas with Boost lambdas we define this.

	for f in `ls *.eps`; do
	convert -density 100 $f -flatten ${f%.*}.png;
	done