Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting warning 'getPayloadItem will be removed in the next major release' #55

Closed
aluzardo opened this issue Sep 16, 2016 · 1 comment
Closed

Comments

@aluzardo
Copy link

The problem is that I see the every time that I run the test one warning in the terminal the warning is

cucumber event handlers attached via registerHandler are now passed the associated object instead of an event
getPayloadItem will be removed in the next major release

One example here

> protractor-cucumber-tests@1.0.0 test-desktop-local /Users/adolfocabrera/xxx/QA-testing/Selenium/xxx
> protractor conf.js --seleniumAddress 'http://localhost:4444/wd/hub'
[10:09:17] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[10:09:17] I/launcher - Running 1 instances of WebDriver
Feature: xxx login
    As a user of xxx login
    I should be able to login in xxx using an existent user

cucumber event handlers attached via registerHandler are now passed the associated object instead of an event
getPayloadItem will be removed in the next major release
 @critical
  Scenario: Check xxx login
    Given The xxx login page is open
    Then The title should contain "xxx"
    And I should be able to login using a xxx user
    And Balance should be displayed
    And Games container should be displayed
    And I should be able to logout

1 scenarios (3 passed)
6 steps (6 passed)
0m43.082s
Report created successfully!
[10:11:23] I/launcher - 0 instance(s) of WebDriver still running
[10:11:23] I/launcher - chrome #01 passed

@darrinholst
Copy link
Contributor

this should be fixed in v1.0.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants