ellimist

Keybase proof

I hereby claim:

• I am ellimist on github.
• I am ellimist (https://keybase.io/ellimist) on keybase.
• I have a public key ASBj6ynA_KpKR_aGgWMcWa8gRsPuJmXmlB9jHmisS0HRNAo

To claim this, I am signing this object:

ellimist

### Keybase proof

I hereby claim:

  * I am ellimist on github.
  * I am ellimist (https://keybase.io/ellimist) on keybase.
  * I have a public key ASAZ5ja9c4vszVV4djs9oIPNY3lWKE5LUFvx_rtbnmIUvQo

To claim this, I am signing this object:

ellimist

# Path to your oh-my-zsh installation.
export ZSH=/Users/dev/.oh-my-zsh

ZSH_THEME="sorin"
plugins=(git zsh-autosuggestions docker docker-compose golang)

source $ZSH/oh-my-zsh.sh

export GOPATH=$HOME/Repos/go
export PATH="$HOME/.rbenv/bin:$PATH"

ellimist

syntax enable

" VUNDLE CONFIG
filetype off
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()
Plugin 'VundleVim/Vundle.vim'

" VUNDLE PLUGINS BELOW

ellimist

set -g default-terminal "screen-256color"
set -g prefix C-a
unbind C-b
bind C-a send-prefix
set -sg escape-time 1
set-option -g base-index 1
setw -g pane-base-index 1

bind | split-window -h
bind - split-window -v

ellimist

#Testing

• Isolate the object under test, don’t test multiple objects under one test case, this creates unneeded code and technical debt.
• Unit test behavior, not methods. We need to know how to use the class to achieve a goal, not how to exercise all the paths through its code.
• Don't test active record, it isn't a special behavior that the system is performing.
• You don't need 100% test coverage all the time.
• Don’t test query messages ( messages that do not modify another object ).
• Do test command messages ( messages that do modify another object ).
• Test the public interface of an object, private methods are always changing and add technical debt to the test and code.
• Mock objects that are outside of the current object test scope (roles, interfaces, other objects)