Commit graph

14 commits

Author SHA1 Message Date
Pat Cavit
c5fac4a51e chore(ospec): merge package.json @ 1.4.0 back 2017-11-29 17:02:26 +01:00
Leo
155fb7bd7a v1.3.1 2017-07-13 19:09:33 -07:00
Pat Cavit
a2390c63fb ospec@1.3.0 2017-07-12 21:05:44 -07:00
Pat Cavit
5660637e30 docs: new repo refs and build tweaks 2017-05-02 13:12:00 -07:00
Leo Horie
9ad16858a5 #1520 ospec: report duplicate test names 2017-01-08 13:05:27 -05:00
Leo Horie
b62663bdc1 ensure properties in arrays are tested #1497 2016-12-31 19:27:23 -05:00
Leo
50b8b498c5 bump ospec version 2016-12-07 18:39:21 -05:00
Leo Horie
f780e0f7b9 bump ospec version 2016-11-15 10:02:25 -05:00
Pat Cavit
71457a356d Fix repository field
https://docs.npmjs.com/files/package.json#repository
2016-11-10 11:01:02 -08:00
Leo Horie
adf91a4f7a update npm identifier 2016-10-31 12:24:46 -04:00
Douglas Brown
d02a238bf0 💁 Adjust ospec bin def, add to README
Getting set up with ospec is deceptively simple, and adding just a bit
more documentation should help new users from falling into the trap of
overthinking the test config.  (I know that I ended up down a very
strange rabbit hole when pulling ospec into a project).

This also adjusts the bin definition in the package file so that we can
hopefully just use the `ospec` command instead of a folder ref.
2016-10-14 13:27:44 -04:00
Leo Horie
b8398544a0 bump ospec version 2016-09-19 14:03:49 -04:00
Pat Cavit
15116d5b2e Update package metadata (#1256) 2016-08-18 09:51:24 -07:00
Pat Cavit
54dc599ca0 Add package.json to ospec so it can be published 2016-08-18 09:36:57 -07:00