Switch off Stacktrace output #696

Mikrovolnovka · 2014-04-10T09:44:29Z

Is there way to switch off the Stacktrace output into console on failures?
e.g.
Current behavior:

Failures:

  1) Components.js Validate Tag Component tutorial on frontend page Element tag
component number 1 has item Text234234
   Message:
     Expected 0 to be greater than 0.
   Stacktrace:
     Error: Expected 0 to be greater than 0.
    at new jasmine.ExpectationResult (c:\Users\dyaroshenko\AppData\Roaming\npm\n
ode_modules\protractor\node_modules\minijasminenode\lib\jasmine-1.3.1.js:137:32)

    at null.toBeGreaterThan (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modul
es\protractor\node_modules\minijasminenode\lib\jasmine-1.3.1.js:1339:29)
    at d:\work\wmg\js-framework-examples\bower_components\factory-testing-framew
ork\modules\helper.js:63:32
    at c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor\node_mod
ules\selenium-webdriver\lib\goog\base.js:1178:15
    at webdriver.promise.ControlFlow.runInNewFrame_ (c:\Users\dyaroshenko\AppDat
a\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdri
ver\promise.js:1598:20)
    at notify (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor\
node_modules\selenium-webdriver\lib\webdriver\promise.js:428:12)
    at notifyAll (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protract
or\node_modules\selenium-webdriver\lib\webdriver\promise.js:397:7)
    at resolve (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor
\node_modules\selenium-webdriver\lib\webdriver\promise.js:375:7)
    at fulfill (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor
\node_modules\selenium-webdriver\lib\webdriver\promise.js:493:5)
    at Object.webdriver.promise.asap (c:\Users\dyaroshenko\AppData\Roaming\npm\n
ode_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:
732:5)

  2) Components.js Validate Tag Component tutorial on frontend page Element tag
component number 2 has item Lisa Simpson
   Message:
     Expected 0 to be greater than 0.
   Stacktrace:
     Error: Expected 0 to be greater than 0.
    at new jasmine.ExpectationResult (c:\Users\dyaroshenko\AppData\Roaming\npm\n
ode_modules\protractor\node_modules\minijasminenode\lib\jasmine-1.3.1.js:137:32)

    at null.toBeGreaterThan (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modul
es\protractor\node_modules\minijasminenode\lib\jasmine-1.3.1.js:1339:29)
    at d:\work\wmg\js-framework-examples\bower_components\factory-testing-framew
ork\modules\helper.js:63:32
    at c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor\node_mod
ules\selenium-webdriver\lib\goog\base.js:1178:15
    at webdriver.promise.ControlFlow.runInNewFrame_ (c:\Users\dyaroshenko\AppDat
a\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdri
ver\promise.js:1598:20)
    at notify (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor\
node_modules\selenium-webdriver\lib\webdriver\promise.js:428:12)
    at notifyAll (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protract
or\node_modules\selenium-webdriver\lib\webdriver\promise.js:397:7)
    at resolve (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor
\node_modules\selenium-webdriver\lib\webdriver\promise.js:375:7)
    at fulfill (c:\Users\dyaroshenko\AppData\Roaming\npm\node_modules\protractor
\node_modules\selenium-webdriver\lib\webdriver\promise.js:493:5)
    at Object.webdriver.promise.asap (c:\Users\dyaroshenko\AppData\Roaming\npm\n
ode_modules\protractor\node_modules\selenium-webdriver\lib\webdriver\promise.js:
732:5)

Finished in 23.552 seconds
7 tests, 3 assertions, 2 failures

Expected behavior:

Failures:

  1) Components.js Validate Tag Component tutorial on frontend page Element tag
component number 1 has item Text234234
   Message:
     Expected 0 to be greater than 0.

  2) Components.js Validate Tag Component tutorial on frontend page Element tag
component number 2 has item Lisa Simpson
   Message:
     Expected 0 to be greater than 0.

Finished in 23.552 seconds
7 tests, 3 assertions, 2 failures

Investigated a bit.

Found that --stackTrace false CLI argument seems not to work

protractor-conf.js options don't work too:

exports.config = {
    ...
    jasmineNodeOpts: {
        ...
        includeStackTrace: false,
        ...
    }
    ...
};

Thanks in advance

The text was updated successfully, but these errors were encountered:

lynndylanhurley · 2014-04-11T02:45:26Z

+1

Too much noise. A simple error takes up like 7 screens. 100 consecutive lines of at <annonymous> does not help me.

Mikrovolnovka · 2014-04-11T09:09:39Z

Yes, me too. Maybe there can be super-improvement to get something like this:

Failures:

  1) Components.js Validate Tag Component tutorial on frontend page Element tag
component number 1 has item Text234234
   Message:
     "Expected 0 to be greater than 0"
     at line XX in file/where/expect/found.js

  2) Components.js Validate Tag Component tutorial on frontend page Element tag
component number 2 has item Lisa Simpson
   Message:
     Expected 0 to be greater than 0.
     at line XY in file/where/expect2/found.js

Finished in 23.552 seconds
7 tests, 3 assertions, 2 failures

juliemr · 2014-04-11T18:45:54Z

The command line option for setting something to false is --no-stackTrace - this is odd, but it's how optimist works. It should probably be better documented, sorry it's hard to find :(

Are you sure changing the config doesn't work though? It's working in Protractor's own tests.

lynndylanhurley · 2014-04-11T19:22:25Z

@juliemr - protractor protractor.conf.js --no-stackTrace and protractor protractor.conf.js both give me the same results:

Here is my protractor config file:

exports.config = {
  // The address of a running selenium server.
  seleniumAddress: 'http://127.0.0.1:4444/wd/hub',

  capabilities: {
    'browserName': 'chrome'
  },

  // Spec patterns are relative to the current working directly when
  // protractor is called.
  specs: ['test/e2e/**/*.coffee'],

  framework: 'mocha',
  baseUrl:   'http://databox-admin.dev',
  stackTrace: false
};

Could this be because I'm using mocha instead of jasmine?

juliemr · 2014-04-11T19:33:53Z

Yes, it's because of mocha. The stack traces option is specific to the test framework, because the test framework is what prints out the results.

It looks like Mocha always outputs stack traces. See mochajs/mocha#545 and openlayers/openlayers#391

lynndylanhurley · 2014-04-11T19:38:35Z

Ahh that makes sense. Thx @juliemr

Mikrovolnovka · 2014-04-14T08:47:39Z

Thanks, @juliemr. I've realized it works fine without --verbose argument.
And is there way to make it work with --verbose?

$ protractor conf/protractor-conf.js --no-stackTrace --verbose

------------------------------------
PID: 14884 (capability: chrome #1)
------------------------------------

Using the selenium server at http://localhost:4444/wd/hub

Components.js


    Before feature: Validate Breadcrumb Component tutorial on frontend page
        Login and open page
        Open page
        Click on FRONTEND item

    Validate Breadcrumb Component tutorial on frontend page
        Click on breadcrumb next item
        Current url contains /component_library/breadddcrumb
        Component tutorial header is Breadcrumb
        tutorial subheader Usage is present
        tutorial subheader Dependencies is present

Failures:

  1) Components.js
    Before feature: Validate Breadcrumb Component tutorial on frontend page Logi
n and open page
   Message:
     Expected false to be true.
   Stacktrace:
     Error: Failed expectation
    at PageObject.login (d:\work\wmg\js-framework-examples\bower_components\fact
ory-testing-framework\pages\login.js:45:109)
    at null.<anonymous> (d:\work\wmg\js-framework-examples\tests\dev_portal\step
s\login.js:5:29)
    at flow.execute.then.e.stack (c:\Users\dyaroshenko\AppData\Roaming\npm\node_
modules\protractor\jasminewd\index.js:36:14)
    at webdriver.promise.ControlFlow.runInNewFrame_ (c:\Users\dyaroshenko\AppDat
a\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdri
ver\promise.js:1598:20)
    at webdriver.promise.ControlFlow.runEventLoop_ (c:\Users\dyaroshenko\AppData
\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriv
er\promise.js:1463:8)

  2) Components.js
    Before feature: Validate Breadcrumb Component tutorial on frontend page Clic
k on FRONTEND item
   Message:
     TypeError: Cannot read property 'ELEMENT' of undefined
   Stacktrace:
     Error
    at steps.components.itClickOnDocsCategory (d:\work\wmg\js-framework-examples
\tests\dev_portal\steps\components.js:9:13)
    at null.<anonymous> (d:\work\wmg\js-framework-examples\bower_components\fact
ory-testing-framework\modules\controller.js:70:32)
...

juliemr · 2014-04-14T17:23:36Z

Nope, verbose overrides stacktrace. This is how jasmine-node set up its reporters - I added an issue to minijasminenode to track this. It will probably get taken care of in the update to Jasmine 2.0. juliemr/minijasminenode#15

Closing this issue, please add comments to the one for minijasminenode!

Shirish2015 · 2015-07-07T18:00:31Z

@juliemr.I am facing the following issue when I'm running my test
script at the time of validation.
Message:
Expected false to be true.
Stacktrace:
Error: Expected false to be true.
at WebdriverIO. (/Users/skumar/projects/reports/test/functional/jasmine-specs/testSuiteSpec.js:33:59)
at WebdriverIO. (/Users/skumar/projects/func-kit/node_modules/webdriverio/lib/utils/PromiseHandler.js:152:26)
at /Users/skumar/projects/func-kit/node_modules/webdriverio/node_modules/chainit/index.js:137:22
at /Users/skumar/projects/func-kit/node_modules/webdriverio/lib/commands/getAttribute.js:93:9
at /Users/skumar/projects/func-kit/node_modules/webdriverio/node_modules/async/lib/async.js:154:25
at WebdriverIO. (/Users/skumar/projects/func-kit/node_modules/webdriverio/lib/commands/getAttribute.js:64:21)
at WebdriverIO. (/Users/skumar/projects/func-kit/node_modules/webdriverio/lib/utils/PromiseHandler.js:152:26)
at /Users/skumar/projects/func-kit/node_modules/webdriverio/node_modules/chainit/index.js:137:22

juliemr added needs: investigation and removed needs: investigation labels Apr 11, 2014

juliemr added component: mocha and removed needs: more info labels Apr 11, 2014

juliemr closed this as completed Apr 14, 2014

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Switch off Stacktrace output #696

Switch off Stacktrace output #696

Mikrovolnovka commented Apr 10, 2014

lynndylanhurley commented Apr 11, 2014

Mikrovolnovka commented Apr 11, 2014

juliemr commented Apr 11, 2014

lynndylanhurley commented Apr 11, 2014

juliemr commented Apr 11, 2014

lynndylanhurley commented Apr 11, 2014

Mikrovolnovka commented Apr 14, 2014

juliemr commented Apr 14, 2014

Shirish2015 commented Jul 7, 2015

Switch off Stacktrace output #696

Switch off Stacktrace output #696

Comments

Mikrovolnovka commented Apr 10, 2014

lynndylanhurley commented Apr 11, 2014

Mikrovolnovka commented Apr 11, 2014

juliemr commented Apr 11, 2014

lynndylanhurley commented Apr 11, 2014

juliemr commented Apr 11, 2014

lynndylanhurley commented Apr 11, 2014

Mikrovolnovka commented Apr 14, 2014

juliemr commented Apr 14, 2014

Shirish2015 commented Jul 7, 2015