네트워크가 찾아낸 것
아래 각 줄은 의견이 아니라 측정입니다. 모두 공개된 샘플로 연결되며, 그 샘플의 contract는 네트워크를 끈 고정 컨테이너에서 실행되므로 직접 다시 돌려 보고 반박할 수 있습니다.
운영체제와 런타임은 연결된 샘플에 실제 기록된 환경을 기준으로 합니다. 해당 값이 없는 항목은 필터 선택 시 제외됩니다.
597개 발견, 8개 생태계.
- cargo
- composer
- gem
- golang
- hex
- npm
- pub
- pypi
샘플이 말하고, 계약이 측정한 것
발행된 샘플이 측정한 결과 중 351–375번째입니다(전체 568개).
-
npm샘플 컨트랙트node · linux/x64marked@17.0.3
믿는 것Markdown image alt text containing double quotes is rendered with HTML entity escaping so the attribute value does not break out of quotes.
측정한 것marked.parse escapes double quotes inside image alt text as " rather than emitting raw unescaped double quotes inside alt attributes
-
npm샘플 컨트랙트node · linux/x64luxon@3.7.2
믿는 것Configuring Settings.defaultZone causes DateTime zone specifiers and setZone calls specifying 'system' to resolve to that configured default zone.
측정한 것When Settings.defaultZone is overridden, Info.normalizeZone('system') and DateTime.fromISO(str, { zone: 'system' }) resolve to the host environment's SystemZone rather than Settings.defaultZone, while 'default' resolves to Settings.defaultZone instead of creating an invalid DateTime.
-
npm샘플 컨트랙트node · linux/x64luxon@3.5.0
믿는 것Setting Settings.defaultZone overrides the zone for DateTime instances created or converted with the system zone specifier.
측정한 것DateTime setZone('system') returns a SystemZone instance with type system rather than inheriting Settings.defaultZone.
-
npm샘플 컨트랙트node · linux/x64luxon@3.6.1
믿는 것Looking up an invalid IANA timezone string such as 'constructor' in Luxon returns an invalid IANAZone object rather than the native Object constructor function.
측정한 것IANAZone.create('constructor') returns an invalid IANAZone instance with isValid equal to false rather than returning the native Object constructor function.
-
npm샘플 컨트랙트node · linux/x64luxon@3.5.0
믿는 것When throwOnInvalid is enabled, Luxon throws public custom error classes whose name property matches their constructor name.
측정한 것Luxon's custom error classes (InvalidDateTimeError, InvalidDurationError, and InvalidIntervalError) are not exported, and their thrown instances have their name property set to 'Error' rather than their constructor names.
-
npm샘플 컨트랙트node · linux/x64luxon@3.7.2
믿는 것DateTime.fromObject parses timezone configuration specified directly inside the date/time units object.
측정한 것DateTime.fromObject throws an Error containing 'Invalid unit zone' if the 'zone' property is passed in the first argument object instead of the second options argument.
-
npm샘플 컨트랙트node · linux/x64jest@30.4.2
믿는 것expect(received).toEqual(expected) and expect(received).toStrictEqual(expected) inspect all own properties on an object, failing when non-enumerable properties or non-enumerable symbols contain conflicting values.
측정한 것expect(received).toEqual(expected) and expect(received).toStrictEqual(expected) pass when two objects differ only in non-enumerable properties or non-enumerable symbols because Jest 30 excludes non-enumerable properties from object matchers by default.
-
npm샘플 컨트랙트node · linux/x64jest@30.4.2
믿는 것Passing an empty array to test.each() safely runs zero tests, mirroring how JavaScript iteration handles empty arrays.
측정한 것Calling test.each([]) throws a fatal error that crashes the test suite, rather than gracefully skipping and running zero tests.
-
npm샘플 컨트랙트node · linux/x64jest@30.4.2
믿는 것A developer might expect that resetting Jest's module cache with jest.resetModules() is sufficient to restore the original implementation of a mocked dependency when the parent module is re-required.
측정한 것jest.resetModules() alone fails to restore the original implementation of a mocked dependency because Jest retains the mock definition in its registry.
-
npm샘플 컨트랙트node · linux/x64jest@29.7.0
믿는 것beforeEach and afterEach hooks run for every test block defined in the file, including concurrent tests.
측정한 것test.concurrent bypasses beforeEach and afterEach hooks, executing concurrent tests without running the setup and teardown hooks.
-
npm샘플 컨트랙트node · linux/x64jest@29.7.0
믿는 것Jest's expect(a).toEqual(b) and expect(a).toStrictEqual(b) perform deep property equality on Error instances and fail when custom error properties differ.
측정한 것expect(errA).toEqual(errB) passes when errA and errB are Error instances with identical messages but different custom properties like code or statusCode.
-
npm샘플 컨트랙트node · linux/x64jest@30.4.2
믿는 것jest.isolateModules isolates module mocking performed with jest.doMock within its callback scope, so subsequent module require calls outside the callback return the unmocked original module.
측정한 것Calling jest.doMock inside a jest.isolateModules callback mutates Jest's global mock registry, causing subsequent require calls outside the callback to receive the mock instead of the original module.
-
npm샘플 컨트랙트node · linux/x64jest@29.7.0
믿는 것Jest automatically clears mock function call history between tests by default.
측정한 것Mock function call history is not cleared between tests by default, so a mock function called in a previous test retains its calls in subsequent tests unless clearMocks is explicitly enabled.
-
npm샘플 컨트랙트node · linux/x64jest@29.7.0
믿는 것Calling jest.spyOn on a getter property without an accessType argument raises a TypeError for non-function properties, or following its error message to use jest.replaceProperty successfully mocks the property value.
측정한 것jest.spyOn on a getter property without accessType throws a base Error rather than a TypeError and suggests using jest.replaceProperty, which then throws another base Error stating it cannot replace getter properties and recommending jest.spyOn(object, property, 'get').
-
npm샘플 컨트랙트node · linux/x64jest@29.7.0
믿는 것A test setup file configured under setupFiles has access to test framework globals like beforeEach, afterEach, and expect.extend.
측정한 것assert running Jest with test framework hooks in setupFiles fails with ReferenceError: beforeEach is not defined because the framework environment is not yet initialized
-
npm샘플 컨트랙트node · linux/x64jest@30.4.2
믿는 것Calling jest.resetAllMocks() restores functions spied on with jest.spyOn() back to their original unmocked implementation.
측정한 것jest.resetAllMocks() clears mock call history and resets the mock implementation to return undefined rather than restoring the original unmocked method, which only jest.restoreAllMocks() or spy.mockRestore() performs.
-
npm샘플 컨트랙트node · linux/x64jest@30.4.2
믿는 것A named ESM import from such a CommonJS module should always resolve to the corresponding own-property function export.
측정한 것Jest 30.4.2 keeps named imports working for a CommonJS module where `module.exports` is a function with own-property exports.
-
npm샘플 컨트랙트node · linux/x64happy-dom@20.11.2
믿는 것Happy DOM writes console output directly to the host console, and filtering virtual console output leaves unmatched entries queued for a later read.
측정한 것A default Window buffers log, warn, and error calls as exact structured entries with type, level, message, and null group metadata
-
npm샘플 컨트랙트node · linux/x64happy-dom@20.11.2
믿는 것The CSS attribute selector [attr~="val"] treats hyphens as word boundaries and matches substrings in hyphenated attribute values.
측정한 것child.matches('[data-controller~="modal"]') returns false against data-controller="modal-auto-close" rather than true, because [attr~="val"] matches only whitespace-separated tokens per CSS Selectors Level 4
-
npm샘플 컨트랙트node · linux/x64express@4.18.2
믿는 것All registered synchronous handlers on a single route will execute in sequence regardless of the stack size exceeding 100 handlers.
측정한 것Express 4.18.2 executes all 105 synchronous handlers registered on a single route, whereas Express 4.18.1 skips the 101st handler due to an off-by-one error during sync stack threshold reset.
-
npm샘플 컨트랙트node · linux/x64express@5.2.1
믿는 것req.is('json') evaluates the Content-Type header directly regardless of whether a body was sent, req.range() returns empty arrays or null on invalid or unsatisfiable byte ranges, and req.accepts() returns true for any media type mentioned in the Accept header.
측정한 것req.is('json') returns null when the request lacks body headers such as Content-Length or Transfer-Encoding even if Content-Type application/json is present, returning the matched type string only when a body is actually transmitted
-
npm샘플 컨트랙트node · linux/x64express@4.22.2
믿는 것Express executes middlewares and route handlers in strict sequential order, preventing subsequent routes from running until preceding async middlewares complete and call next().
측정한 것A downstream route handler is executed before a preceding async middleware completes if an earlier middleware calls next() twice.
-
npm샘플 컨트랙트node · linux/x64es-toolkit@1.50.0
믿는 것Passing { leading: true, trailing: false } to debounce executes immediately on the first call and prevents delayed execution on the trailing edge.
측정한 것Passing { leading: true, trailing: false } to es-toolkit debounce fails to invoke immediately because edges defaults to ['trailing'] unless configured as { edges: ['leading'] }, while trailing execution still fires on timeout.
-
npm샘플 컨트랙트node · linux/x64express@4.21.2
믿는 것Express identifies error-handling middleware by checking if the first argument is an error or omitting the unused next parameter like (err, req, res) still catches errors passed to next(err).
측정한 것Express skips 3-parameter error handlers (err, req, res) during error routing because it identifies error middleware solely by checking fn.length === 4, executing only 4-parameter functions (err, req, res, next) while running 3-parameter functions on normal requests with shifted arguments
-
npm샘플 컨트랙트node · linux/x64core-js@3.50.0
믿는 것A core-js-provided URL.prototype.toJSON dynamically calls the current URL.prototype.toString, so reassigning toString later also changes toJSON output.
측정한 것When the host URL.prototype.toJSON is absent, importing core-js/actual/url installs the method while retaining a compliant native URL constructor.
여기 있는 줄을 확인하는 방법
샘플을 열고 contract를 읽고 실행하십시오. contract는 그 샘플 자신의 테스트입니다. 네트워크를 끈 고정 컨테이너에서 실행되고, 그 실행의 서명된 영수증이 네트워크에 저장됩니다. 여기 있는 어떤 것도 라이브러리에 대한 우리의 해석에 기대지 않습니다. 라이브러리가 실제로 한 일에만 기댑니다.
게시된 샘플 중 일부는 이 페이지에 없습니다. 계약은 통과했고 샘플도 살아 있지만, 그 계약에 문장으로 읽힐 줄이 없기 때문입니다. expect(x).toBe(1) 같은 단언은 그것이 검사하는 믿음 옆에 놓아도 독자에게 아무것도 말해주지 않습니다. 읽을 수 없는 근거를 싣기보다는 뺀다는 쪽을 택했습니다.