(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
The definition of Unit Test is quite general:
In computer programming, unit testing is a method by which individual units of source code, sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures are tested to determine if they are fit for use. [...] A unit could be an entire module, but it is more commonly an individual function or procedure. --Wikipedia
#!/usr/bin/env python3 | |
# -*- coding: utf-8 -*- | |
# Author: Damien Garaud | |
# Date: 2014-2015 | |
# License: Simplified BSD | |
"""Allow you to pipe command results into an Emacs buffer. Suppose you have an | |
Emacs server since you launch 'emacsclient'. |
Custom recipe to get OS X 10.10 Yosemite running from scratch, setup applications and developer environment. I use this gist to keep track of the important software and steps required to have a functioning system after a semi-annual fresh install. On average, I reinstall each computer from scratch every 6 months, and I do not perform upgrades between distros.
This keeps the system performing at top speeds, clean of trojans, spyware, and ensures that I maintain good organizational practices for my content and backups. I highly recommend this.
You are encouraged to fork this and modify it to your heart's content to match your own needs.
This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].
We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.
Each commit message consists of a header, a body, and a footer.
/** | |
* Cancellable promise. | |
* | |
* @class CancellablePromise | |
* @constructor | |
* @extends {Promise} | |
* @param {Function} fn A function where to insert the logic that resolves this | |
* promise. Receives `fulfill` and `reject` functions as parameters. This | |
* function is called synchronously. | |
* @param {Function} opt_errorCallback Optional error callback to be fired |
#!/bin/bash | |
#requires jq -> http://stedolan.github.io/jq/ | |
#optional change working_dir | |
working_dir=${1-$(pwd)} | |
cd $working_dir | |
user="github_username" | |
token="application token" | |
organization="Organization_Name" |
""" | |
Test (data) migrations in Django. | |
This uses py.test/pytest-django (the `transactional_db` fixture comes from there), | |
but could be easily adopted for Django's testrunner: | |
from django.test.testcases import TransactionTestCase | |
class FooTestcase(TransactionTestCase): | |
def test_with_django(self): |
Livros sobre Estratégias de Testes, meus favoritos: | |
- The "A" Word, Under the Covers of Test Automation: https://leanpub.com/TheAWord | |
// Super recomendo também o blog do Alan Page (http://angryweasel.com/blog/) que tem muuuita coisa legal e o podcast que ele fez recentemente com o Joe Colantonio (basicamente e destila em 50 min grande parte das ideias dele sobre automação e QA): http://joecolantonio.com/testtalks/44-alan-page-testing-software-at-microsoft-lessons-learned/ | |
- Working Effectively with Unit Tests: https://leanpub.com/wewut | |
// Esse livro me ajudou muuito!!! Os conceitos de Solitary and Sociable Tests que o cara descreve são super úteis para entender como usar mocks e como montar uma estratégia de testes automatizados eficientes. | |
- A Practitioner's Guide to Software Test Design: http://www.amazon.com/Practitioners-Guide-Software-Test-Design/dp/158053791X/ | |
// Basicamente toda a base teórica necessária para "desenhar" casos de testes caixa branca e caixa preta eficientes. A "Section II - White |