joelove

Writing tests for validators

I've broken down the validation architecture in to its absolute simplest form so we can use it to understand and compare testing approaches.

The validation architecture

Let's say we have a set of simple validation functions that fail whatever you pass in:

validations.js

joelove

Form validators

Form validators are comprised of validation rules. Each of these rules receive:

• The name of a field or collection to validate
• A unique, human-readable key to describe the validation
• A function that validates the field or collection
• An optional function to validate the entire form data object
• An optional function to combine the results of the main validation result and the form data validation result

alexeygrigorev

import requests
import base64
from tqdm import tqdm


master_json_url = 'https://178skyfiregce-a.akamaihd.net/exp=1474107106~acl=%2F142089577%2F%2A~hmac=0d9becc441fc5385462d53bf59cf019c0184690862f49b414e9a2f1c5bafbe0d/142089577/video/426274424,426274425,426274423,426274422/master.json?base64_init=1'
base_url = master_json_url[:master_json_url.rfind('/', 0, -26) + 1]

resp = requests.get(master_json_url)
content = resp.json()

nuflowx

If you don't want the black bars on a video in your site these might do the trick for you:

```
@media all and (min-aspect-ratio: 16/9) {
  .video {
    width: 100vw;
    height: calc(100vw * (9/16));
  }
}
@media all and (max-aspect-ratio: 16/9) {

alexpchin

// sending to sender-client only
socket.emit('message', "this is a test");

// sending to all clients, include sender
io.emit('message', "this is a test");

// sending to all clients except sender
socket.broadcast.emit('message', "this is a test");

// sending to all clients in 'game' room(channel) except sender

patik

Squashing Git Commits

The easy and flexible way

This method avoids merge conflicts if you have periodically pulled master into your branch. It also gives you the opportunity to squash into more than 1 commit, or to re-arrange your code into completely different commits (e.g. if you ended up working on three different features but the commits were not consecutive).

Note: You cannot use this method if you intend to open a pull request to merge your feature branch. This method requires committing directly to master.

Switch to the master branch and make sure you are up to date: