An in-range update of babel-cli is breaking the build 🚨

Version 6.23.0 of babel-cli just got published.

Branch	Build failing 🚨
Dependency	babel-cli
Current Version	6.22.2
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-cli is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of nightwatch is breaking the build 🚨

Version 0.9.17 of nightwatch was just published.

Branch	Build failing 🚨
Dependency	nightwatch
Current Version	0.9.16
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

nightwatch is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v0.9.17

#1604 - Fixes compatibility issues with latest Selenium Server

Commits

The new version differs by 2 commits.

4aa6aa2 0.9.17
e5a81a6 #1604 - Implemented a fix to support latest selenium server versions

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of moment is breaking the build 🚨

Version 2.19.0 of moment was just published.

Branch	Build failing 🚨
Dependency	moment
Current Version	2.18.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

moment is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of appium is breaking the build 🚨

Version 1.6.5 of appium just got published.

Branch	Build failing 🚨
Dependency	appium
Current Version	1.6.4
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As appium is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

1.6.5

Appium 1.6.5 fixes many issues and continues the trend to make more aspects of
the automation process configurable.

General

Add --enable-heapdump server flag to turn on NodeJS memory dump collection,
to aid in memory management.
Better logging of erroneous responses.
Full support of W3C specification's handling of capabilities.
Fix licensing in all dependencies.

Android

Fix backgrounding of app.
Add androidInstallPath capability to specify where on the device apps are installed.
Speed up taking screenshots on Android 5.0 and higher devices.
Fix handling of activity names that are inner classes.
Support latest Android SDK directory structure.
Fix issue where granting permissions would fail if there were too many.
Fix handling of parent element information when finding elements.

Android - UIAutomator 2

Fix handling of boolean return values.
Add skipUnlock capability to skip the device unlock process.
Fix issue where setting the network connection would crash.

iOS

Add enableAsyncExecuteFromHttps capability to allow simulators to execute
asynchronous JavaScript on pages using HTTPS.
Allow setting url in native context, for opening deep links.
Better memory management when capturing device logs.
Add webkitResponseTimeout capability to adjust the timeout for responses in
Safari real device tests.
Add enablePerformanceLogging capability (previously Android-only) to turn on
performance logging in Safari tests.

iOS - XCUITest

Fully support clearSystemFiles desired capability, deleting the derived data
for the xcodebuild process.
Fix longPress duration, to be milliseconds.
Add mobile: selectPickerWheelValue method to aid in interacting with picker wheels.
Add mobile: alert method to enable passing of buttonLabel option, to handle
alerts with non-standard button names.
Fix hanging if an app is not installed and only bundle identifier is given in
capabilities.
Allow platformVersion to be a number or a string.

Commits

The new version differs by 28 commits.

145ccfb Update CHANGELOG and version for 1.6.5 release (#8536)
5578af0 Update shrinkwrap 1.6
5106422 update description for waitForActivity
9efe30b Add documentation about Chromedriver (#8476)
6eaba9c add event timing docs
6661ab2 Document various reset strategies (#8459)
41bae13 Use updated GCC in travis (#8467)
79b3117 Add documentation for ‘mobile: touchAndHold’ endpoint (#8446)
c3329dd make triagers list public so we can instruct triager to pull from it
cea118f Add documentation on mobile: alert script (#8368)
22c1b30 small fix for markdown format (#8369)
630286c expand backgroundApp docs with info from #7741
c75f44f Move enablePerformanceLogging cap to general (#8354)
95431b0 Add license status and report
bc358d3 Remove date-utils library and use node-dateformat (#8328)

There are 28 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Update README docs with new custom commands

There have been recent commits to commands/mobile/ that have not been added to the README. For instance, #100

Btw, this repo is awesome...thanks for making something so simple to integrate with NW.

Set custom screenshot output path

I using this library through Magellan and I am having trouble setting the screenshot path to anything besides the default ./temp. In settings.js, it suggests passing--screenshots=path/to/temp/screenshot/directory, but that doesn't have any effect. I also tried using --screenshot_path=path/to/temp/screenshot/directory to match what the code appears to be looking for. Any suggestions?

I am calling my tests like this...

"./node_modules/.bin/magellan --local_browsers chrome --serial --screenshot_path "./test-data""

An in-range update of bluebird is breaking the build 🚨

Version 3.5.1 of bluebird just got published.

Branch	Build failing 🚨
Dependency	bluebird
Current Version	3.5.0
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

bluebird is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes

v3.5.1

Bugfixes:

Fix false positive unhandled rejection when using async await (#1404)
Fix false positive when reporting error as non-error (#990)

Commits

The new version differs by 26 commits.

dcfa52b Release v3.5.1
48c8591 Fixes #1404
3c93a91 Revert "Update default.html"
5155a7b Merge pull request #1463 from gabegorelick/isError
3f7ccf4 Better error check
f8f4a01 Merge pull request #1462 from themez/patch-1
18891c9 Fix title style
b2b14c2 Update default.html
a61aa1c tiny grammar change (#1457)
2c9f7a4 Update tap.md (#1438)
3a7fcbb fixes markdow headers (#1437)
e889c0d Correct a tiny tiny typo (#1431)
e03f12c improve .all() docs (#1436)
4f90934 Updated links (#1420)
3d2e57f Add Node.js 7+8 to Travis build matrix (#1412)

There are 26 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

update babel version to 7

babel is in devDep can you remove it or update it

waitForMobileElVisible missing?

I was reviewing the nightwatch-extra docs, and do not see a waitForMobileElVisible command. Is there one available that can be passed an accessibility id? I'll probably need to add a custom implementation if this is not available out of the box. Any help would be greatly appreciated. Thanks!

An in-range update of babel-cli is breaking the build 🚨

Version 6.26.0 of babel-cli just got published.

Branch	Build failing 🚨
Dependency	babel-cli
Current Version	6.24.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

babel-cli is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ codecov/patch Coverage not affected. Details
❌ codecov/project No report found to compare against Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of geckodriver is breaking the build 🚨

Version 1.7.1 of geckodriver just got published.

Branch	Build failing 🚨
Dependency	geckodriver
Current Version	1.7.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As geckodriver is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 3 commits.

44c322e 1.7.1
520f9e5 Authors and Changelog update
2632ae7 Add support for a binary CDN location (#25)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Remove ESLint packages from dependencies

I noticed that eslint packages are specified in dependencies:

nightwatch-extra/package.json

Lines 90 to 92 in 5f77e4c

    
           "eslint": "^3.12.2", 
        
           "eslint-config-walmart": "^1.1.0", 
        
           "eslint-plugin-filenames": "^1.1.0",

These are then downloaded alongside the testarmada-nightwatch-extra package, but don't appear to actually be used. Can these be moved to devDependencies?

An in-range update of chromedriver is breaking the build 🚨

Version 2.32.1 of chromedriver just got published.

Branch	Build failing 🚨
Dependency	chromedriver
Current Version	2.32.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As chromedriver is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits.

2cd4573 Bump version to 2.32.1
2ade3f4 Fixed bug where ca string encased in double quotes was not parsed properly

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Nightwatch page objects for native apps

Do nightwatch-extra mobile commands for native apps work out of the box when using the Nightwatch page object implementation?

Under the hood, Nightwatch (latest release) switches between xpath, css selector or recursion modes when interpreting page object command methods. However, if I need to to use accessibility id or name locator strategies, for example, there are no global methods (in the same vein as useXpath or useCss) available to do so.

Currently, I'm seeing the following error when triggering a page object command using a mobile custom command:

Error processing the server response:
 Parameters were incorrect. We wanted {"required":["using","value"]} and you sent ["using"]
INFO Response 400 POST /wd/hub/session/5409ec9d-3d45-477c-b241-869020a880fb/element (4ms) { value: -1, error: 'Unexpected token P in JSON at position 0' }
INFO Request: POST /wd/hub/session/5409ec9d-3d45-477c-b241-869020a880fb/element
 - data:  {"using":"LOG IN"}
 - headers:  {"Content-Type":"application/json; charset=utf-8","Content-Length":18}
[HTTP] --> POST /wd/hub/session/5409ec9d-3d45-477c-b241-869020a880fb/element
[HTTP] {"using":"LOG IN"}
[debug] [MJSONWP] Bad parameters: BadParametersError: Parameters were incorrect. We wanted {"required":["using","value"]} and you sent ["using"]
[HTTP] <-- POST /wd/hub/session/5409ec9d-3d45-477c-b241-869020a880fb/element 400 1 ms - 90
[HTTP]

PageObject File looks like the following:

  elements: {
    logInButton: {
      locateStrategy: 'name',
      selector: 'LOG IN'
    }
  },

  commands: [{
    clickLoginBtn: function () {
      this.clickMobileEl('@logInButton')

      return this
    }
  }]
}

An in-range update of testarmada-magellan-saucelabs-executor is breaking the build 🚨

Version 1.0.4 of testarmada-magellan-saucelabs-executor just got published.

Branch	Build failing 🚨
Dependency	testarmada-magellan-saucelabs-executor
Current Version	1.0.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As testarmada-magellan-saucelabs-executor is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 1 commits .

41e0086 remove selenium server version for firefox

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

nightwatch-extra does not support Nightwatch 1.x

When upgrading to nightwatch 1.0.0 or subsequent, the new api loader does not like the current way the testarmada assertions are written. I get this error:

The assertion module needs to contain an .assertion() method

which seems to come from here: https://github.com/nightwatchjs/nightwatch/blob/b3e1e1846ccabe806f54ab2bd8821b55e4e425ce/lib/api-loader/assertion.js#L43-L47

which suggests that instead of exporting the entire class, if the assertion files just exported the assertion function as module.exports.assertion, this would work with Nightwatch 1.x

An in-range update of selenium-server is breaking the build 🚨

Version 3.5.0 of selenium-server just got published.

Branch	Build failing 🚨
Dependency	selenium-server
Current Version	3.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As selenium-server is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 2 commits.

4752522 updated to 3.5.0
7d82246 use package version to generate the name of the jar file

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

transpiling step during "npm install"

same as TestArmada/magellan-saucelabs-executor#25

https://github.com/TestArmada/nightwatch-extra/blob/master/package.json#L16

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

There's no need to explicitly refer to `./node_modules/.bin`

same as TestArmada/magellan-saucelabs-executor#26

An in-range update of mocha is breaking the build 🚨

Version 3.5.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.4.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/travis-ci/push The Travis CI build passed Details
✅ codecov/patch Coverage not affected. Details
❌ codecov/project No report found to compare against Details

Release Notes

free-as-in-freezing

3.5.0 / 2017-07-31

📰 News

Mocha now has a code of conduct (thanks @kungapal!).
Old issues and PRs are now being marked "stale" by Probot's "Stale" plugin. If an issue is marked as such, and you would like to see it remain open, simply add a new comment to the ticket or PR.
WARNING: Support for non-ES5-compliant environments will be dropped starting with version 4.0.0 of Mocha!

🔒 Security Fixes

#2860: Address CVE-2015-8315 via upgrade of debug (@boneskull)

🎉 Enhancements

#2696: Add --forbid-only and --forbid-pending flags. Use these in CI or hooks to ensure tests aren't accidentally being skipped! (@charlierudolph)
#2813: Support Node.js 8's --napi-modules flag (@jupp0r)

🔩 Other

Various CI-and-test-related fixes and improvements (@boneskull, @dasilvacontin, @PopradiArpad, @Munter, @ScottFreeCode)
"Officially" support Node.js 8 (@elergy)

Commits

The new version differs by 34 commits.

82d879f Release v3.5.0
bf687ce update mocha.js for v3.5.0
ec73c9a update date for release of v3.5.0 in CHANGELOG [ci skip]
1ba2cfc update CHANGELOG.md for v3.5.0 [ci skip]
065e14e remove custom install script from travis (no longer needed)
4e87046 update karma-sauce-launcher URL for npm@5
6886ccc increase timeout for slow-grepping test
2408d90 Make dependencies use older version of readable-stream to work around incompatibilities introduced by 2.3.0 on June 19th
68a1466 Try not clearing the env for debug in the integration test and see if that fixes Node 0.10 on AppVeyor; if need be, some other fix/workaround can be applied to handle whatever was up with debug without causing this issue
958fbb4 Update new tests to work in browser per test hierarchy reorganization
1df7c94 Merge pull request #2704 from seppevs/increase_test_coverage_of_mocha_js
1f270cd Stop timing out (#2889)
27c7496 upgrade to [email protected]; closes #2859 (#2860)
50fc47d fix CI; closes #2867 (#2868)
1b1377c Add test for ignoreLeaks and fix descriptions

There are 34 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Getting Error 'this.client.assertion' is not a function

I am working on setting up automation test for an application using nightwatch. When i run the tests, getEl function call fails at - /node_modules/testarmada-nightwatch-extra/lib/base-command.js in the below line of pass function -

this.client.assertion(true, pactual, pexpected, _util2.default.format(message, this.time.totalTime), true);

and the error is **TypeError: this.client.assertion is not a function.
Wondering whether i missed anything in the config.
Appreciate any help.

	"eslint": "^3.12.2",
	"eslint-config-walmart": "^1.1.0",
	"eslint-plugin-filenames": "^1.1.0",

testarmada / nightwatch-extra Goto Github PK

nightwatch-extra's People

Contributors

Stargazers

Watchers

Forkers

nightwatch-extra's Issues

Version 6.23.0 of babel-cli just got published.

Version 0.9.17 of nightwatch was just published.

Version 2.19.0 of moment was just published.

Version 1.6.5 of appium just got published.

General

Android

Android - UIAutomator 2

iOS

iOS - XCUITest

Version 3.5.1 of bluebird just got published.

Version 6.26.0 of babel-cli just got published.

Version 1.7.1 of geckodriver just got published.

Version 2.32.1 of chromedriver just got published.

Version 1.0.4 of testarmada-magellan-saucelabs-executor just got published.

Version 3.5.0 of selenium-server just got published.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

Version 3.5.0 of mocha just got published.

3.5.0 / 2017-07-31

📰 News

🔒 Security Fixes

🎉 Enhancements

🔩 Other

Recommend Projects

Recommend Topics

Recommend Org