aerospike-client-nodejs tested by Argusic Runner

Attempt 1 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of aerospike-client-nodejsaerospikedatabase-driverjavascriptnodejsnosql

Session recording

Loading recording...

Download the original recording · fingerprint abff66fc0dd776ce...

What the test found

Aerospike Node.js client v6.7.1 compiled and links correctly against locally-built C client v4deb88e. The native .node binary loads in Node.js 18.19.1, exports all expected API surfaces (client, Key, connect, filter, lists, maps, etc.), and 98 of 99 noserver unit tests pass (1 pre-existing string mismatch). Full integration tests require a running Aerospike server.

Standard npm install plus building C client from source. Needed to supply zlib1g-dev and libyaml-dev headers by downloading debs (no root). Static libs required rebuilding with -fPIC. Node v18 is below the README-declared minimum (Node 20,22,24,25) so some npm deps had to be downgraded to CJS-compatible versions. The single test failure (1/99) is a pre-existing trailing-period string mismatch in an error message, not a regression.

Argusic installed aerospike-client-nodejs in 14 minutes and launched it; verification reached Verified with mock services. 8 of 8 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of aerospike-client-nodejs

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion