From 2cfab3565f5c563bc1be8795dd222f57c4373b6d Mon Sep 17 00:00:00 2001 From: Jason Williams Date: Thu, 30 Oct 2014 15:40:23 +0000 Subject: [PATCH] Handle null/undefined value in test assertion. No Issue. - Test is not guaranteed to get a setting that has a "value" so we need to handle the case where it's null or undefined. --- core/test/integration/model/model_settings_spec.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/test/integration/model/model_settings_spec.js b/core/test/integration/model/model_settings_spec.js index 3932969f35..cb77c5281f 100644 --- a/core/test/integration/model/model_settings_spec.js +++ b/core/test/integration/model/model_settings_spec.js @@ -43,7 +43,7 @@ describe('Settings Model', function () { }).then(function (found) { should.exist(found); - found.get('value').should.equal(firstSetting.attributes.value); + should(found.get('value')).equal(firstSetting.attributes.value); found.get('created_at').should.be.an.instanceof(Date); done();