richarcher

const pluralize = (word, count) => `${count} ${word}${count === 1 ? '' : 's'}`

// filtering out the consoles - '.' for a pass, 'F' for a fail, and '*' for a skipped test

// wholesale stolen/adapted from https://github.com/jodonnell/jest-simple-dot-reporter

// usage npm test -- --reporters="<rootDir>/dev_scripts/oz-simple-jest-reporter.js"

class OzSimpleJestReporter {
    constructor(globalConfig, options) {

richarcher

Keybase proof

I hereby claim:

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

To claim this, I am signing this object:

richarcher

In the initial planning phase of the Agents project, we decided to rebuild along the principles of Progressive Enhancement.

##What is Progressive Enhancement?

"Progressive Enhancement" takes the stance that the various aspects of a website - the content, the presentation, and the behaviour is to be developed separately on top of one another in layers with the content of a site as the foundation. Should one of these aspects fail to function, they should fall away and still make it possible for content to be available to users.

There can be many reasons for these failures: broken or outdated browsers, unsupported hardware, disabled or blocked assets, interrupted network connectivity, or just good old-fashioned bugs in code.

In a typical site built using Progressively Enhanced principles, there should be a basic, "un-enhanced" version available as a fallback should the enhanced features fail. A fallback can take several forms, and range in levels of sophistication: