Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings
This repository was archived by the owner on Jul 29, 2024. It is now read-only.

Commit df3dd64

Browse files
alan-agius4Keen Yee Liau
authored and
Keen Yee Liau
committed
fix: remove elementExplorer api and command line
Protractor debugger and element explorer cannot be used for Node.js 8+ and were removed in version 7.
1 parent c1e31e8 commit df3dd64

File tree

4 files changed

+2
-97
lines changed

4 files changed

+2
-97
lines changed

‎bin/elementexplorer.js

Lines changed: 0 additions & 46 deletions
This file was deleted.

‎docs/debugging.md

Lines changed: 0 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -258,51 +258,6 @@ used from the browser's console.
258258
> window.clientSideScripts.findInputs('username', document.getElementById('#myEl'));
259259
```
260260

261-
**Testing Out Protractor Interactively**
262-
263-
When debugging or first writing test suites, you may find it helpful to
264-
try out Protractor commands without starting up the entire test suite. You can
265-
do this with the element explorer.
266-
267-
To run element explorer, simply run protractor as you normally would, but pass in
268-
the flag --elementExplorer:
269-
270-
protractor --elementExplorer
271-
272-
This will load up the URL on WebDriver and put the terminal into a REPL loop.
273-
You will see a > prompt. The `browser`, `element` and `protractor` variables will
274-
be available. Enter a command such as:
275-
276-
> browser.get('http://www.angularjs.org')
277-
278-
or
279-
280-
> element(by.id('foobar')).getText()
281-
282-
Typing tab at a blank prompt will fill in a suggestion for finding
283-
elements. You can also use the `list(locator)` command to list all elements
284-
matching a locator.
285-
286-
Element explorer will start chrome by default. However, you can specify
287-
another browser, change browser settings, or specify any other config that you
288-
normally would with your protractor test. To do this, pass configs to
289-
protractor like you normally would,
290-
but with the `--elementExplorer` flag set:
291-
292-
protractor [configFile] [options] --elementExplorer
293-
294-
For example, to connect to ChromeDriver directly, use
295-
296-
protractor --directConnect --elementExplorer
297-
298-
Element explore will ignore your specs, not set up your framework (e.g. jasmine,
299-
mocha, cucumber), and only allow you to pass in 1 capability, but will honor
300-
every other parameter in your config.
301-
302-
Note `baseUrl` is used here as the initial page, i.e. element explorer will try
303-
to navigate to `baseUrl` automatically on start.
304-
305-
306261
## Taking Screenshots
307262

308263
WebDriver can snap a screenshot with `browser.takeScreenshot()`. This can be a

‎lib/cli.ts

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,6 @@ let allowedNames = [
9999
'nodeDebug',
100100
'debuggerServerPort',
101101
'frameworkPath',
102-
'elementExplorer',
103102
'debug',
104103
'logLevel',
105104
'disableChecks',
@@ -134,7 +133,6 @@ let yargsOptions: any = {
134133
framework: 'Test framework to use: jasmine, mocha, or custom',
135134
resultJsonOutputFile: 'Path to save JSON test result',
136135
troubleshoot: 'Turn on troubleshooting output',
137-
elementExplorer: 'Interactively test Protractor commands',
138136
debuggerServerPort: 'Start a debugger server at specified port instead of repl',
139137
disableChecks: 'Disable cli checks',
140138
logLevel: 'Define Protractor log level [ERROR, WARN, INFO, DEBUG]'
@@ -148,7 +146,6 @@ let yargsOptions: any = {
148146
build: 'capabilities.build',
149147
grep: 'jasmineNodeOpts.grep',
150148
'invert-grep': 'jasmineNodeOpts.invertGrep',
151-
explorer: 'elementExplorer'
152149
},
153150
strings: {'capabilities.tunnel-identifier': ''}
154151
};
@@ -232,7 +229,7 @@ if (!configFile) {
232229
}
233230
}
234231

235-
if (!configFile && !argv.elementExplorer&&args.length < 3) {
232+
if (!configFile && args.length < 3) {
236233
console.log(
237234
'**you must either specify a configuration file ' +
238235
'or at least 3 options. See below for the options:\n');

‎lib/launcher.ts

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -159,8 +159,7 @@ let initFn = function(configFile: string, additionalConfig: Config) {
159159
});
160160
})
161161
.then(() => {
162-
// 3) If we're in `elementExplorer` mode, run only that.
163-
if (config.elementExplorer || config.framework === 'explorer') {
162+
if (config.framework === 'explorer') {
164163
if (config.multiCapabilities.length != 1) {
165164
throw new Error('Must specify only 1 browser while using elementExplorer');
166165
} else {

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /