Mirror of datashard/snapshot, a Cypress JSON Snapshot Utiliy Plugin
Find a file
2024-05-02 21:07:42 +02:00
.github Expand Readme, remove Gleb, up version number 2024-04-25 13:01:00 +02:00
cypress tests: have test fixtures use single snapshot folder 2024-05-02 21:07:42 +02:00
src chore: add ability to contain snapshots in a single snapshot folder 2024-05-02 21:07:19 +02:00
.gitignore make devtoolslog a let because it breaks code @ work 2023-03-28 12:41:33 +02:00
.npmignore finish most writings 2024-04-25 14:09:41 +02:00
.npmrc fix not being able to push 2023-03-18 11:01:43 +01:00
cypress.config.js chore: add ability to contain snapshots in a single snapshot folder 2024-05-02 21:07:19 +02:00
LICENSE finish most writings 2024-04-25 14:09:41 +02:00
package-lock.json bump cypress and redo logging 2024-02-01 11:58:42 +01:00
package.json Expand Readme, remove Gleb, up version number 2024-04-25 13:01:00 +02:00
README.md finish most writings 2024-04-25 14:09:41 +02:00
renovate.json Commit changes: update package name, remove Travis config, and modify snapshot-spec.js 2023-02-20 20:14:01 +01:00

@datashard/snapshot

Adds JSON Snapshot comparison to Cypress

⚠️ Breaking Changes ⚠️

  • With V3, the readFileMaybe task has been removed, we now rely on cy.fixture internally.
  • the previous SNAPSHOT_UPDATE Environment/Config Variable has been changed to updateSnapshots

[!DANGER] This means that previous tests will likely be broken, please make sure that your tests pass before updating to the latest version of this Plugin.

This current release will be released as 3.0.0-beta, should Bugs be found by me or my Employer, I will open Issues/PRs to fix those, should anyone else find Bugs/Edgecases, etc. please open an Issue.

Install

Requires Node 16 or above

npm i --save-dev @datashard/snapshot

Import

After Installing, you'll need to add the following import into your Commands/Support File

by default this will be cypress/support/e2e.js

require('@datashard/snapshot').regsiter()

This will register a new Command .snapshot(), to create and compare JSON Snapshots.

Config

You can pass updateSnapshots and useFolders as options in the cypress.config.js file

Example Settings for the Module Alternatively, you can also add snapshotUpdate as an Environment Variable to update your snapshots.

Simply pass --env updateSnapshots=true when running Cypress.

Usage

If properly added, usage of this plugin is rather simple, just add .snapshot() to cypress functions that return valid JSON. (i.e. cy.wrap)

When properly added, you can chain .snapshot() off of cy functions like cy.wrap, just make sure they return valid JSON.

Example

describe("my test", () => {
  it("works", () => {
    cy.log("first snapshot");
    cy.wrap({ foo: 42 }).snapshot("foo");
    cy.log("second snapshot");
    cy.wrap({ bar: 101 }).snapshot("bar");
  });
});

This Plugin will then save your snapshots as

// useFolders: false
cypress/fixtures/my-test__works__foo.json
cypress/fixtures/my-test__works__bar.json

// useFolders: true
cypress/fixtures/my-test/works/foo.json
cypress/fixtures/my-test/works/bar.json

// {fixtureFolder}/<Context>-<Describe>-<It>-<Name?>.json
// {fixtureFolder}/<Context>/<Describe>/<It>/<Name?>.json

Snapshots will generally be saved using this the Convention mentioned in the Comment of the above Codeblock, which is provided by the named Cypress Test Steps.

Passing a name to the Snapshot function is required, but not checked, if you want to take multiple snapshots in the same block.

If you have two or more Snapshots in the same Block, the next one WILL always overwrite the previous one while updating, causing the First Snapshot in the Block to Fail. While running your Tests, if a value changed, it will, of course, no longer match the snapshot and throw an Error.

Which will look like this:

When the Test succeeds, it will instead log a Success in the Log and let you know where the File has been saved to, relative to the Fixture Snapshot Folder