ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Coffee​Script Ddry Snippets

by ddry ST2/ST3

CoffeeScript snippets for ddry data-driven DRY Node JS testing wrapper

Labels snippets

Details

  • 1.0.1
  • github.​com
  • github.​com
  • 7 months ago
  • 53 minutes ago
  • 7 months ago

Installs

  • Total 272
  • Win 99
  • OS X 105
  • Linux 68
Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6 Dec 5 Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8 Nov 7 Nov 6 Nov 5 Nov 4 Nov 3 Nov 2 Nov 1
Windows 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 1 0 0 0 1 0 1 2 1 2 0 0 1 0 1 1 0 2 0 0 2 1
OS X 1 0 0 1 2 0 0 0 0 3 0 3 1 0 0 0 0 0 1 0 0 0 0 0 2 0 1 2 1 0 0 1 1 0 1 0 1 0 1 1 1 0 0 0 1 0
Linux 1 0 0 0 1 0 0 0 0 2 1 0 0 0 0 1 0 0 0 0 0 2 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 2 0 0

Readme

Source
raw.​githubusercontent.​com

Sublime Text CoffeeScript snippets for ddry

ddry logo

Set of CoffeeScript snippets for ddry data-driven DRY Node JS testing wrapper.

Scope of all these snippets is source:coffee, so please save your brand new data-driven spec file as .coffee to enable them.

Then, even if you haven't decided yet what are you going to test, ddp tab will expand to

Error: language “coffee” is not supported
'use strict'

module.exports = (dd) ->
  dd.drive [
    dd.pending()
  ]

This spec is very promising since it can actually engage every test harness, but sadly useless.

To start actual testing, expand dd tab it tab to

Error: language “coffee” is not supported
'use strict'

module.exports = (dd) ->
  dd.drive [
    it: 'get things done'
    i: [ input ]
    e: expected
  ]

Then cit will give you comma and the next it object, so please start it at correct indent level.

Use ddr to start just dd.drive call, ddc for dd.context. And we have now only minor snippets left.

Matchers

  • m: for matcher: 'plain'
  • m:a for matcher: 'anyOrder'
  • m:c for matcher: 'contains'
  • m:e for matcher: 'error'
  • m:p for matcher: 'property'

Hooks

  • bh for before hook
  • ah for after hook

Keep focused and save your time.