chore(test): move element_spec off of the control flow

[CrispusDH]

• note that JSHint still does not support async ... await - Support for async functions jshint/jshint#2604 . It might be better to move to ESLint
• add try ... catch
• add await
• all tests were passed locally using directConnect: true
• I get flaky EPIPE errors for .filter(), .map(), .reduce() methods - there are several issues that related to it (there are related to concurrent requests issues, not for async ... await

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[CrispusDH]

I signed it!

[googlebot]

CLAs look good, thanks!

[googlebot]

CLAs look good, thanks!

[cnishina]

Thanks for this. I found some issues with my work. This was a great commit either way. If you want to help out, I'm going to work on:

• locators_spec.js
• lib_spec.js
• mockmodule_spec.js

and then I'll jump around to other tests in the suite.

This means in the basic, I will not touch these files if you want to take a shot at them. Please work on one file at a time as a pull request.

• expected_conditions_spec.js
• handling_spec.js
• navigation_spec.js
• polling_spec.js
• restart_spec.js
• synchronize_spec.js

Also a quick review of the PR submitted, it looks like you have a lot of trailing spaces on lines. If you are using visual studio code, there is a setting to remove trailing settings. (https://stackoverflow.com/questions/30884131/remove-trailing-spaces-automatically-or-with-a-shortcut)

I'll also add this to the tracking issue. Thanks again!