Kevin Zehnder k-zehnder

A Typical directory structure for running tests using `unittest`

The best solution in my opinion is to use the unittest [command line interface][1] which will add the directory to the sys.path so you don't have to (done in the TestLoader class).

For example for a directory structure like this:

new_project

├── antigravity.py

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

	from sqlalchemy import Column, Integer, String, ForeignKey, create_engine
	from sqlalchemy.ext.declarative import declarative_base
	from sqlalchemy.orm import relationship, backref, sessionmaker, joinedload

	# For this example we will use an in-memory sqlite DB.
	# Let's also configure it to echo everything it does to the screen.
	engine = create_engine('sqlite:///:memory:', echo=True)

	# The base class which our objects will be defined on.
	Base = declarative_base()

	/**
	* @param {Object} settings
	* - {String} current
	* - {Object} states
	* - {Object} actions
	* @constructor
	*/
	function StateMachine(settings) {
	this._current = settings.initState
	this.actions = settings.actions

	import requests
	from flask import Flask
	from flask import request, send_from_directory
	from twilio import twiml

	from martianify import martianify

	UPLOAD_FOLDER = '/path/to/your/project/'

	# App declaration and configuration

	#!/usr/bin/env python
	# -- coding: utf-8 --
	import json
	from flask import Flask, url_for
	from flask_sqlalchemy import SQLAlchemy

	"""
	Flask-SQLAlchemy many-to-many relationship using helper table
	http://flask-sqlalchemy.pocoo.org/2.1/models/
	Hippies love their dogs.

	## I'm working on a project using Flask to access a database and then
	## pass on query data to a client where the data will be graphed
	## in the browser.
	## I wanted to enable users to retrieve the graph data
	## in a csv file after clicking a button on the client.
	## This is a generalized version of how I did it:

	# imports other than Flask
	import csv
	from sqlalchemy import create_engine

	<!-- create a folder named templates, put this file into it -->
	<!DOCTYPE html>
	<title>Upload File</title>
	<h1>Photo Upload</h1>
	<form method="POST" enctype="multipart/form-data">
	{{ form.hidden_tag() }}
	{{ form.photo }}
	{% for error in form.photo.errors %}
	<span style="color: red;">{{ error }}</span>
	{% endfor %}

	import * as sinon from 'sinon';
	import * as Mongoose from 'mongoose';
	import { expect } from 'chai';

	// test utility
	function areObjectIdsEqual(id1: Mongoose.Types.ObjectId \| string, id2: Mongoose.Types.ObjectId \| string) {
	let normalizedId1: Mongoose.Types.ObjectId = new Mongoose.Types.ObjectId(id1.toString());
	let normalizedId2: Mongoose.Types.ObjectId = new Mongoose.Types.ObjectId(id2.toString());
	return normalizedId1.equals(normalizedId2);
	}

Kevin Zehnder k-zehnder

A Typical directory structure for running tests using unittest

System Design Cheatsheet

Basic Steps

General rules

Design rules

A Typical directory structure for running tests using `unittest`