npmpackage.info

Gathering detailed insights and metrics for @s-ui/mockmock

@s-ui/mockmock - 2.7.0 | npmpackage.info

@s-ui/mockmock

Monorepo for SUI (Simple User Interface) packages.

2.7.0

173

JavaScript

12.35 kB

3.1

Installations

npm install @s-ui/mockmock

Developer Guide

BETA

Typescript

No

Module System

CommonJS, UMD

Node Version

20.18.3

NPM Version

10.8.2 Pull Requests

Open

21

Total

1,776

Closed

225

Merged

1,530

Issues

Open

18

Total

157

Closed

139

Releases

Unable to fetch releases

Languages

JavaScript

SCSS

TypeScript

HTML

CSS

Makefile

Smarty

Dockerfile

Sass

JavaScript (95.46%)

SCSS (2.23%)

TypeScript (1.89%)

HTML (0.14%)

CSS (0.14%)

Makefile (0.07%)

Smarty (0.05%)

Dockerfile (0.01%)

Sass (0.01%)

Developer

SUI-Components

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

173 Stars

9,682 Commits

35 Forks

40 Watchers

58 Branches

78 Contributors

Updated on Jul 09, 2025

Maintainers

View All 78 Contributors

Package Meta Information

Latest Version

2.7.0

Package Id

@s-ui/mockmock@2.7.0

Unpacked Size

12.35 kB

Size

3.79 kB

File Count

NPM Version

10.8.2

Node Version

20.18.3

Published on

Jul 09, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

nock sinon

Dev Dependencies

axios

sui-mockmock

Mocking utilities for testing.

⚠️ It is highly recommended to use sui-mock instead of this package. It could be deprecated in the future.

Motivation

Centralize common solutions for common mocking concerns in JavaScript.

Installation

1npm install @s-ui/mockmock --save-dev

Available mockers

http

Mocks http requests in node and XMLHttpRequest requests in the browser.

Usage

1import {HttpMocker} from '@s-ui/mockmock'
2import axios from 'axios'
3
4// Mock any requests
5const mocker = new HttpMocker()
6mocker
7  .httpMock('http://fake.api.com')
8  .get('/my-service')
9  .reply({property: 'value'}, 200)
10
11// Make your requests
12axios
13  .get('http://fake.api.com/my-service')
14  .then(response => console.log(response)) // { property: 'value' }

Also available for import

1import HttpMocker from '@s-ui/mockmock/lib/http'

Details

Since this library internally constructs the url of the original and the mocked request and then compares them, it's needed to create the mock request with the same parameter order than the original, if not, it will throw a 404.

The parameters of both petitions (original and mocked) don't have the same parameter order (err 404 thrown)

1mocker
2  .httpMock(...)
3  .get('/urlToAttack')
4  .query({
5    search: 'value of the search',
6    working: false,
7  })
8  ...
9  ...
10
11domain
12  .get('attacks_the_same_url_use_case')
13  .execute({
14    working: false,
15    search: 'value of the search',
16  })
17  ...
18  ...

The mocked and the original HTTP requests have to same parameter order

1mocker
2  .httpMock(...)
3  .get('/urlToAttack')
4  .query({
5    search: 'value of the search',
6    working: true,
7  })
8  ...
9  ...
10
11domain
12  .get('attacks_the_same_url_use_case')
13  .execute({
14    search: 'value of the search',
15    working: true,
16  })
17  ...
18  ...

Clean up state

It is important to clean tests before and after so you have a initial state non dependent.

Why? Sharing mutable state between components it is a bad idea.

One tests depends on the others, so you can not run one test in isolation.
If you refactor one test, you might break all the others tests, because all tests are part of a chain of actions.
If tests are isolated you can: paralelize test and remove or add tests without breaking other ones

Example:

1
2describe('abc', () => {
3  beforeEach(() => {
4    mocker.create()
5  })
6  afterEach(() => {
7    mocker.restore()
8  })
9  ...
10  it('xyz', () =>{
11    ...
12  })
13})
14

Mocking Requests

The .reply(response, statusCode, headers) method causes the 'fake' server to respond to any request not matched by another response with the provided data.

1mocker
2  .httpMock(...)
3  .get('/urlToAttack')
4  .query({
5    search: 'value of the search',
6    working: true,
7  })
8  .reply('{status: "ok"}', 200, {'Access-Control-Allow-Credentials': true})
9  ...
10  ...
11
12const response = domain
13  .get('attacks_the_same_url_use_case')
14  .execute({
15    search: 'value of the search',
16    working: true,
17  })
18
19expect(response.data.status).to.equal('ok')

Retriving Requests

If you want to test what your use_case, function, etc is doing, probably you will need to check that based on the arguments provided to the function are transformed and as an output or side effect one or various requests are done will a certain url, body, or headers.

The .requestNTH(index) method returns the nth request mocked by the fake server so you can assert things like:

The content of the body of the request is the one expected.
The headers of the request are the expected.
The url of the request is the one expected.
The order of the requests is the correct one.

1mocker
2  .httpMock(...)
3  .get('/urlToAttack')
4  .query({
5    search: 'value of the search',
6    working: true,
7  })
8  .reply('{status: "ok"}', 200, {'Access-Control-Allow-Credentials': true})
9  ...
10  ...
11
12const response = domain
13  .get('attacks_the_same_url_use_case')
14  .execute({
15    search: 'value of the search',
16    working: true,
17  })
18
19const request = mock.requestNTH(0)
20expect(request.body).to.be.equal('year=2030&doors=3&color=blue')
21expect(request.url).to.be.equal('https://.../urlToAttack')
22...

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

3

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 3

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/labeled_pull_request.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/labeled_pull_request.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/labeled_pull_request.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/labeled_pull_request.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/labeled_pull_request.yml:38: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/labeled_pull_request.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/main.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/main.yml/master?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/main.yml:32: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/main.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:58: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/main.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/main.yml:64: update your workflow using https://app.stepsecurity.io/secureworkflow/SUI-Components/sui/main.yml/master?enable=pin
Warn: containerImage not pinned by hash: packages/sui-test-e2e/Dockerfile:1: pin your Docker image by updating cypress/browsers to cypress/browsers@sha256:95587c1ce688ce6f59934cc234a753a32a1782ca1c7959707a7d2332e69f6f63
Warn: npmCommand not pinned by hash: packages/sui-test-e2e/Dockerfile:5
Warn: npmCommand not pinned by hash: .github/workflows/labeled_pull_request.yml:33
Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 2 third-party GitHubAction dependencies pinned
Info: 0 out of 1 containerImage dependencies pinned
Info: 3 out of 5 npmCommand dependencies pinned

0

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

License

Determines if the project has defined a license.

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3.1

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More