akromio / nodejs-doubles Goto Github PK

Package name

No response

Please, describe the feature.

Right now, for getting the first call and second calls of a monitor log, we need to use getCall(0) and getCall(1), respectively.
It seems better to use firstCall and secondCall properties, similarly to the expected package.

Please, describe what problem solving.

Consistence with the expected package.

The following error is raised when a simulator with a simulated method is used:

 TypeError: target.apply is not a function
      at Object.apply (node_modules/@akromio/doubles/dist/cjs/monitor/index.js:72:28)
      at CatalogInstaller.installCatalog (dist/cjs/CatalogInstaller.js:74:44)
      at Context.<anonymous> (__tests__/unit/CatalogInstaller.js:76:45)
      at processImmediate (node:internal/timers:466:21)

Package name and version

@akromio/doubles 0.5.1

Environment

$ gattuso s
OS: linux (5.15.0-56-generic) #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022
Arch: x64
Node.js: v18.9.0

Describe the bug

The method Monitor.hasToBeMonitorized() is failing when a Symbol is received as name. This parameter can be text and Symbol.

Expected behavior

The method must not fail if a symbol is received.

Actual behavior

The method is failing and the test is failing due to this issue.

Backtrace

No response

Reproduction Steps

No response

Additional information

No response

Package name

@akromio/doubles

Please, describe the feature.

We should add method.sleep() for resolving a value after a delay:

method.sleep("100ms", "the-value")

Please, describe what problem solving.

Do resolve several issues needed of a delay.

Package name

No response

Please, describe the feature.

We must support the readable streams.

Please, describe what problem solving.

Needed due to readable streams are very used.

Package name

No response

Please, describe the feature.

We need to support writable streams.

Please, describe what problem solving.

Writable streams are very used.

Package name

@akromio/doubles

Please, describe the feature.

It's common to do log.getCall(2), for this reason, we need to define thirdCall.

Please, describe what problem solving.

Improve ease of use.