From b5a57b40f7b7eee699670d6e1db1716f1bdeed4a Mon Sep 17 00:00:00 2001 From: Garrett Johnson Date: Sat, 3 Nov 2012 17:12:11 -0400 Subject: [PATCH] test.js: smembers reply should not assume order, b/c sets do not ensure order Closes #326. Signed-off-by: DTrejo --- test.js | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/test.js b/test.js index 94bd19d682..2e802b6b63 100644 --- a/test.js +++ b/test.js @@ -994,16 +994,16 @@ tests.SADD2 = function () { client.sadd("set0", ["member0", "member1", "member2"], require_number(3, name)); client.smembers("set0", function (err, res) { assert.strictEqual(res.length, 3); - assert.strictEqual(res[0], "member0"); - assert.strictEqual(res[1], "member1"); - assert.strictEqual(res[2], "member2"); + assert.ok(~res.indexOf("member0")); + assert.ok(~res.indexOf("member1")); + assert.ok(~res.indexOf("member2")); }); client.SADD("set1", ["member0", "member1", "member2"], require_number(3, name)); client.smembers("set1", function (err, res) { assert.strictEqual(res.length, 3); - assert.strictEqual(res[0], "member0"); - assert.strictEqual(res[1], "member1"); - assert.strictEqual(res[2], "member2"); + assert.ok(~res.indexOf("member0")); + assert.ok(~res.indexOf("member1")); + assert.ok(~res.indexOf("member2")); next(name); }); };