Product
Socket Now Supports uv.lock Files
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
snap-shot-core
Advanced tools
Save / load named snapshots, useful for tests
This is the snapshot loading and saving utility, used by snap-shot and schema-shot projects. Can be used to save snapshots from any testing project.
npm install --save-dev snap-shot-core
const snapShot = require('snap-shot-core')
const what // my object
const out = snapShot({
what,
file: __filename, // aliases: file, __filename
specName: 'my test', // or whatever name you want to give,
store, // optional function to preprocess the value before storing
compare: compareFn, // optional function that compares values
raiser: raiseErrorFn, // optional
ext: '.test' // default value is '.snapshot'
})
Sometimes you want to store not the value itself, but something derived,
like the object's schema (check out schema-shot). You can
pass a function store
that transforms the object before saving.
For example if we are only interested in the type of value, we can do the
following (paired with the right compare
function).
const store = x => typeof x
// expected - previously saved "type of" value
// value - current original value
const compare = ({expected, value}) => ({
valid: typeof value === expected,
message: 'check the type'
})
snapShot({
what,
store,
compare
})
The comparator function needs to compare two values and return an object. Here is an example
const compareFn = ({expected, value}) => {
const e = JSON.stringify(expected)
const v = JSON.stringify(value)
if (e === v) {
return {
valid: true
}
}
return {
valid: false,
message: `${e} !== ${v}`
}
}
The above function will be used by default or you can pass your own function
that expects ({expectd, value})
and returns either {valid: true}
or
{valid: false, message: 'to throw as error'}
Default function will compare current and loaded values using compare
function and if the values are different will throw an error. You can provide
your own function to fail a test differently. Your function will be called
with these parameters
raiser({
value, // current value
expected, // loaded value
specName, // the name of the test
compare // compare function
})
Default raiser
function just throws an Error with good message.
The snapShotCore
function returns the expected value.
If this is the first time, it will be store(what)
value. Otherwise it will be the loaded expected
value.
You can pass several options to control the behavior. I usually grab them from the environment variables.
show
- log snapshot value when saving new onedryRun
- only show the new snapshot value, but do not save itupdate
- override snapshot value with the new one if there is differenceci
- the tests are running on CI, which should disallow saving snapshotsconst opts = {
show: Boolean(process.env.SHOW),
dryRun: Boolean(process.env.DRY),
update: Boolean(process.env.UPDATE),
ci: Boolean(process.env.CI)
}
snapShot({
what,
file: __filename,
specName: 'my test',
compare: compareFn,
ext: '.test',
opts
})
If opts.ci
is not set, it will use is-ci
to determine if running on CI or not.
Run the code with DEBUG=snap-shot-core
option to see more log messages.
In case you execute your tests in watch mode and you notice the snapshots are always new-created for the same set of tests, then you need to restore the counters per file.
tape example:
//foo.test.js
const test = require('tape');
const snapShot = require('snap-shot-core')
test.onFinish(snapShot.restore)
test('one test', function (t) {
t.plan(1)
snapShot({
what: 1,
file: __filename,
specName: 'one test'
})
})
Author: Gleb Bahmutov <gleb.bahmutov@gmail.com> © 2017
License: MIT - do anything with the code, but don't blame me if it does not work.
Support: if you find any problems with this module, email / tweet / open issue on Github
Copyright (c) 2017 Gleb Bahmutov <gleb.bahmutov@gmail.com>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
FAQs
Save / load named snapshots, useful for tests
The npm package snap-shot-core receives a total of 4,411 weekly downloads. As such, snap-shot-core popularity was classified as popular.
We found that snap-shot-core demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.