Paul MelnikowandGitHub
a0c43ed219
This is a bit of sugar that reduces the boilerplate for creating testers in what I expect will become the standard case: a service in `foo/foo-thing.service.js` with its tests in `foo/foo-thing.tester.js`. This makes a small stylistic change, which is to name the service by its CamelCase class name rather than an invented snake-case ID. Whereas before the name was specified in `class FooThing extends Base[Json]Service` and a second time in the tester, it now only needs to be specified once.
23 lines
520 B
JavaScript
23 lines
520 B
JavaScript
'use strict'
|
|
|
|
const Joi = require('joi')
|
|
const createServiceTester = require('../create-service-tester')
|
|
|
|
const { isVPlusDottedVersionAtLeastOne } = require('../test-validators')
|
|
|
|
const t = createServiceTester()
|
|
module.exports = t
|
|
|
|
t.create('version (valid)')
|
|
.get('/formatador.json')
|
|
.expectJSONTypes(
|
|
Joi.object().keys({
|
|
name: 'gem',
|
|
value: isVPlusDottedVersionAtLeastOne,
|
|
})
|
|
)
|
|
|
|
t.create('version (not found)')
|
|
.get('/not-a-package.json')
|
|
.expectJSON({ name: 'gem', value: 'not found' })
|