New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

test-machinepack

Package Overview
Dependencies
Maintainers
1
Versions
40
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

test-machinepack - npm Package Compare versions

Comparing version 2.1.9 to 2.1.10

6

package.json
{
"name": "test-machinepack",
"author": "Mike McNeil <@mikermcneil>",
"version": "2.1.9",
"version": "2.1.10",
"description": "Raw test runner for machinepacks (also includes a simple stub test driver)",

@@ -21,5 +21,5 @@ "keywords": [

"lodash": "3.9.1",
"machine": "~11.0.3",
"machine": "^12.2.1",
"machinepack-machines": "6.3.0",
"rttc": "~9.3.4"
"rttc": "^9.4.0"
},

@@ -26,0 +26,0 @@ "repository": {

@@ -1,5 +0,3 @@

// TODO: pull this into mp-machines
module.exports = require('machine').build({
var testMachine = {
identity: 'test-machine',

@@ -57,9 +55,14 @@

description: 'The return value could not be stringified into JSON - perhaps it contains circular references?',
example: {
message: 'Output returned by the `finglebär` machine\'s "foobar" exit could not be stringified...etc',
outcome: 'success',
output: '===',
inspectedOutput: '{ stuff: "things" }',
duration: 2948
}
extendedDescription:
'Note that we use the `===` exemplar here. This is necessary because it is the simplest '+
'way to represent `output: undefined`. Even if we set the `output` facet to `===`, since '+
'the base value for the ref type is `null` as of rttc@9.3.0, that wouldn\'t work either.',
example: '===',
// {
// message: 'Output returned by the `finglebär` machine\'s "foobar" exit could not be stringified...etc',
// outcome: 'success',
// output: '===?', (but could also be undefined)
// inspectedOutput: '{ stuff: "things" }',
// duration: 2948
// }
},

@@ -69,3 +72,8 @@

description: 'The test failed because the result was not the expected output and/or the expected outcome.',
variableName: 'failureReport',
outputFriendlyName: 'Failure report',
extendedDescription:
'Note that we use the `===` exemplar for `actual` here. This is necessary because it is '+
'the simplest way to represent `actual.output === undefined`. Even if we set the `output` '+
'facet to `===`, since the base value for the ref type is `null` as of rttc@9.3.0, that '+
'wouldn\'t work either.',
example: {

@@ -81,8 +89,9 @@ message: 'Expected outcome was "success" but actually the machine triggered its "error" exit.',

}],
actual: {
outcome: 'success',
output: '===',
inspectedOutput: '{ stuff: "things" }',
duration: 2948
}
actual: '===',
// {
// outcome: 'success',
// output: '===?' (but also could be `undefined`),
// inspectedOutput: '{ stuff: "things" }',
// duration: 2948
// }
}

@@ -93,9 +102,15 @@ },

description: 'The test was successful.',
variableName: 'whatActuallyHappened',
example: {
outcome: 'success',
output: '===',
inspectedOutput: '{ stuff: "things" }',
duration: 2948
}
outputFriendlyName: 'What actually happened',
outputDescription: 'A dictionary reporting the actual outcome, output, duration, etc.',
extendedDescription:
'Note that we use the `===` exemplar here. This is necessary because it is the simplest '+
'way to represent `output: undefined`. Even if we set the `output` facet to `===`, since '+
'the base value for the ref type is `null` as of rttc@9.3.0, that wouldn\'t work either.',
example: '===',
// {
// outcome: 'success',
// output: '===?' (but also could be `undefined`),
// inspectedOutput: '{ stuff: "things" }',
// duration: 2948
// }
}

@@ -383,5 +398,2 @@

};
var Machine = require('machine');
module.exports = Machine.build(testMachine);
});
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc