![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
nock-record-next
Advanced tools
Small wrapper around Nock Back, with improved ergonomics.
:heavy_check_mark: Testing framework agnostic
:heavy_check_mark: Types included
:heavy_check_mark: Works with promises (so enables async/await
)
If you're familiar with Jest Snapshots, the following workflow should feel familiar.
nock
will be created on subsequent test runs, based on the previous recordingimport { setupRecorder } from "nock-record";
import { getGithubProfile } from "./githubProfile";
const record = setupRecorder();
describe("#getGithubProfile", () => {
it("should retrieve user info", async () => {
// Start recording, specify fixture name
const { completeRecording, assertScopesFinished } = await record("github-edorivai");
// Run your function under test
const result = await getGithubProfile("edorivai");
// Complete the recording, allow for Nock to write fixtures
completeRecording();
// Optional; assert that all recorded fixtures have been called
assertScopesFinished();
// Perform your own assertions
expect(result).toMatchSnapshot();
});
});
Sets up your recorder
// Signature:
function setupRecorder(options?: RecorderOptions): Record;
// Usage:
const record = setupRecorder({ mode: 'record' });
option | default | description |
---|---|---|
fixturePath | {test-directory}/__nock-fixtures__ | The directory where fixtures will be stored |
mode | record | "wild" | "dryrun" | "record" | "lockdown" See official docs for details |
Starts recording HTTP requests
// Signature:
function record(fixtureName: string, options: nock.NockBackOptions = {}): Promise<Recording>;
// Usage:
const recording = await record("your-fixture-name");
Returned from a call to record
property | type | description |
---|---|---|
completeRecording | () => void | Tells Nock to complete the recording and write any fixtures |
assertScopesFinished | () => void | Asserts whether all recorded scopes have finish |
scopes | Nock.Scope[] | All Nock Scopes associated with this recording |
const { completeRecording, assertScopesFinished } = await record("your-fixture-name");
await yourFunctionThatSendsRequests();
completeRecording();
assertScopesFinished();
Clone this repo, then run:
npm install
npm run build
npm run test-examples
FAQs
Small wrapper around Nock Back, with improved ergonomics.
The npm package nock-record-next receives a total of 1 weekly downloads. As such, nock-record-next popularity was classified as not popular.
We found that nock-record-next 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.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.