isVerbose has no effect

[ceelian]

isVerbose does not display a more verbose output.
I hoped that we would see something like the test suite filenames which are processed, or the describe and it texts.

My config file is:

exports.config = {
        seleniumAddress: 'http://localhost:4444/wd/hub',
        baseUrl: 'http://localhost:8080',
        framework: 'jasmine2',
        jasmineNodeOpts: {
            // If true, print colors to the terminal.
            showColors: true,
            isVerbose: true
        },
        params: testing_params,
        specs: ['test/e2e/stories/*.story.js'],
        onPrepare: function() {
            global.browser2 =  browser.forkNewDriverInstance();
        }

Output with isVerbose: false:

protractor prot.js --specs test/e2e/stories/test.story.js 
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver
Started


.


1 spec, 0 failures
Finished in 4.616 seconds
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 passed

Output with isVerbose: true:

protractor prot.js --specs test/e2e/stories/test.story.js 
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver
Started


.


1 spec, 0 failures
Finished in 4.207 seconds
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 passed

System OS X, Protractor Version 1.6.1

Thx.

[hankduan]

isVerbose is not a jasmine2 feature as we're using https://github.com/jasmine/jasmine-npm directly now. See https://github.com/angular/protractor/blob/master/docs/referenceConf.js#L280 for jasmine2 options

[juliemr]

Closing as answered.

[ceelian]

@hankduan, @juliemr can you give a clue how to activate a more verbose output with protractor and Jasmine 2 or give a best practice?

Our experience is that just "F"'s in a row of "." are not very useful in large projects with dozens of test suites when you have to figure out in which test case and test file the failure occurred.

[hankduan]

What does your output look like? Jasmine should already point you to 1) which spec failed 2) error message and 3) stack trace

i.e.:

$ node lib/cli.js spec/hankConf.js --suite=hank
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver
Started
F.

Failures:
1) test do authenticated tests authenticated test 1
  Message:
    Expected true to be false.
  Stack:
    Error: Failed expectation
        at Env.<anonymous> (/workspace/protractor/spec/hank_spec.js:7:20)
        at /workspace/protractor/node_modules/jasminewd2/index.js:95:14
        at [object Object].webdriver.promise.ControlFlow.runInNewFrame_ (/workspace/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1654:20)
        at [object Object].webdriver.promise.ControlFlow.runEventLoop_ (/workspace/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1518:8)
        at [object Object].wrapper [as _onTimeout] (timers.js:252:14)
        at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

2 specs, 1 failure
Finished in 0.09 seconds
[launcher] 0 instance(s) of WebDriver still running
[launcher] chrome #1 failed 1 test(s)
[launcher] overall: 1 failed spec(s)
[launcher] Process exited with error code 1

[ceelian]

Unfortunately not in all cases. E.g. when an element can't be found because it is not visible, there is no spec file mentioned where this happened.

[...]
2) Projects List Site changes url to project single
  Message:
    Failed: element not visible
      (Session info: chrome=40.0.2214.111)
      (Driver info: chromedriver=2.13.307650 (feffe1dd547ee7b5c16d38784cd0cd679dfd7850),platform=Mac OS X 10.9.5 x86_64) (WARNING: The server did not provide any stacktrace information)
    Command duration or timeout: 15 milliseconds
    Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:02:37'
    System info: host: 'karin.office.cnc', ip: '192.168.123.102', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.9.5', java.version: '1.7.0_45'
    Session ID: d9b5991356abecf991317557cbd9162b
    Driver info: org.openqa.selenium.chrome.ChromeDriver
    Capabilities [{platform=MAC, acceptSslCerts=true, javascriptEnabled=true, browserName=chrome, chrome={userDataDir=/var/folders/wx/qt_77kv53270dwfh0s15vbg40000gn/T/.org.chromium.Chromium.6YxstT}, rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, version=40.0.2214.111, takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, webStorageEnabled=true, nativeEvents=true, applicationCacheEnabled=false, takesScreenshot=true}]
  Stack:
    Error: Failed: element not visible
      (Session info: chrome=40.0.2214.111)
      (Driver info: chromedriver=2.13.307650 (feffe1dd547ee7b5c16d38784cd0cd679dfd7850),platform=Mac OS X 10.9.5 x86_64) (WARNING: The server did not provide any stacktrace information)
    Command duration or timeout: 15 milliseconds
    Build info: version: '2.44.0', revision: '76d78cf', time: '2014-10-23 20:02:37'
    System info: host: 'karin.office.cnc', ip: '192.168.123.102', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.9.5', java.version: '1.7.0_45'
    Session ID: d9b5991356abecf991317557cbd9162b
    Driver info: org.openqa.selenium.chrome.ChromeDriver
    Capabilities [{platform=MAC, acceptSslCerts=true, javascriptEnabled=true, browserName=chrome, chrome={userDataDir=/var/folders/wx/qt_77kv53270dwfh0s15vbg40000gn/T/.org.chromium.Chromium.6YxstT}, rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, version=40.0.2214.111, takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, webStorageEnabled=true, nativeEvents=true, applicationCacheEnabled=false, takesScreenshot=true}]
        at /usr/local/lib/node_modules/protractor/node_modules/jasminewd2/index.js:104:16
        at /usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/base.js:1582:15
        at [object Object].webdriver.promise.ControlFlow.runInNewFrame_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1654:20)
        at notify (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:465:12)


3) Projects Single Site Enter 3 Questions and delete one
  Message:
[...]

[hankduan]

Thanks for the clarification. I haven't tried to reproduce yet, but if that's the case it's a bug. Jasmine should report the stack trace under 'non-verbose' mode for these errors.

[hankduan]

Fixed here: #1795

background:
related: jasmine/jasmine#734
The code for protractor is already in place, and we were waiting for jasmine to release the new version to support this. For now, you can just apply the change to your machine (i.e. npm install jasmine 2.2.1) and it should automagically work.