DeMarko

Title	Have It?	Transcribed	Content
What Lies Ahead	X	X	Whizzard
Trace Amount	X	Not transcribing	Excerpt from Android: Free Fall
Cyber Exodus	X	X	Chaos Theory
A Study in Static	X	Not transcribing	Excerpt from Android: Golem (The Identity Trilogy)
Humanity's Shadow	X	X	Andromeda
Future Proof	X	Not transcribing	Excerpt from Android: Strange Flesh
Creation and Control	X	X / X	Thomas Haas / Rielle "Kit" Peddler
Opening Moves	X	X	Press Release / For Immediate Release

peterhurford

Using py.test is great and the support for test fixtures is pretty awesome. However, in order to share your fixtures across your entire module, py.test suggests you define all your fixtures within one single conftest.py file. This is impractical if you have a large quantity of fixtures -- for better organization and readibility, you would much rather define your fixtures across multiple, well-named files. But how do you do that? ...No one on the internet seemed to know.

Turns out, however, you can define fixtures in individual files like this:

tests/fixtures/add.py

import pytest

@pytest.fixture

CristinaSolana

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

joshbuchea

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example