BACKSTOP CHROME-HEADLESS BETA VERSION IS HERE! #479

garris · 2017-07-20T06:11:07Z

ATTENTION BACKSTOPPERS!

📣 BackstopJS now supports all existing features using chrome-headless.

I have been working with chrome-headless extensively for the past 6 weeks now and I am happy to report to you that it is WICKED STABLE.

BackstopJS been major-version-bumped to 3.x.x. (legacy mode is deprecated)

Check it out here!

npm install -g backstopjs@beta

Documentation is in progress now. Examples and feature tests are here for the moment...

https://github.com/garris/backstop-feature-tests/

All beta users: Please keep in mind that the chrome-headless feature is built on top of chromy.js https://github.com/OnetapInc/chromy. Any onBefore and onReady scripts will need to use chromy.js syntax and methods in order to work when using the chrome option. I have personally been in touch with @dotneet of chromy.js -- he is very dedicated to the project and has been a huge help supporting this integration!

The chrome-headless feature is able to capture screen shots in parallel -- This is already 3x faster than the previous version. There are other additions listed in the brandh readme file.

LET THE BUG BASHING BEGIN!

closes #454

The text was updated successfully, but these errors were encountered:

daveaspinall · 2017-07-20T10:43:26Z

Hi Garris,

So happy to see Chromy support! Thanks for making this happen 🙌🏻

I've just grabbed backstopjs@beta to try it out and it runs much slower than the slimerjs/phantomjs engines? Running backstop reference on a single scenario in three viewports, and I must get a screenshot every 10-15 seconds. Scenario config is below (everything else is from backstop genConfig) :

    {
      "label": "Chromy",
      "url": "/styleguide.html",
      "hideSelectors": [
        "[data-shop-map]",
        "[data-search-map]"
      ],
      "removeSelectors": [
        ".sg-pattern-head",
        ".sg-pattern-extra"
      ],
      "selectorExpansion": true,
      "selectors": [
        ".sg-pattern"
      ],
      "readyEvent": null,
      "delay": 500,
      "misMatchThreshold" : 0.1,
      "requireSameDimensions" : true
    }

"engine": "chromy",
"report": ["browser"]

Any specific config that would be slowing this down?

Primajin · 2017-07-20T12:09:12Z

mirzazeyrek · 2017-07-20T12:25:29Z

That's really great news. But about onReady.js and onBefore.js files I'm not sure if it's possible to convert those or how :)

BTW, I noticed beta branch on github doesn't have chromy updates.

garris · 2017-07-20T13:57:22Z

@daveaspinall I am surprised to hear that -- in my environment, running the backstop-feature-tests it is the opposite... could you open a ticket and include console output for both the chrome and the phantom versions?

Thanks!

daveaspinall · 2017-07-20T14:46:24Z

@garris sure no problem 🙂

The page it's testing does have quite a few selectors (~52 elements), but there must be something with my setup as it took over 20mins and still hadn't finished 🙈

garris · 2017-07-20T15:48:30Z

@mirzazeyrek -- yes, as I mentioned -- the scripts are totally different and I don't know yet if there is an easy way to automatically convert or polyfill. That said, please check out this test repo https://github.com/garris/backstop-feature-tests/ for examples of setting cookies and manipulating DOM. We have already converted some complex scripts at work and did not find it to be too difficult. @dotneet has been very helpful with questions and feature tweaks as well. I am working on documentation now and will probably help with chromy documentation where I can.

garris · 2017-07-20T15:55:13Z

@daveaspinall I see. please post your example -- I think there is a selector expansion feature optimization I can add which would significantly improve performance for that many selectors in one scenario.

klausbayrhammer · 2017-07-20T19:16:54Z

@garris this is amazing news! We'll give it a try tomorrow!

kiran-redhat · 2017-07-25T01:51:38Z

Sharp dependency issue for BackstopJS. I've raised this issue with Sharp lovell/sharp#879 but mentioning here too.

Unable to install sharp on Amazon Linux AMI (4.9.17-8.31.amzn1.x86_64) related release notes:
https://aws.amazon.com/amazon-linux-ami/2017.03-release-notes/.

Steps to reproduce:

Be on Amazon Linux AMI
git clone https://github.com/garris/BackstopJS.git
cd BackstopJS
git checkout backstop-chromy
npm install

More info:
4497 verbose about to build /home/myusername/BackstopJS/node_modules/sharp
4498 info build /home/myusername/BackstopJS/node_modules/sharp
4499 info linkStuff sharp@0.18.2
4500 silly linkStuff sharp@0.18.2 has /home/myusername/BackstopJS/node_modules as its parent node_modules
4501 verbose linkBins sharp@0.18.2
4502 verbose linkMans sharp@0.18.2
4503 verbose rebuildBundles sharp@0.18.2
4504 verbose rebuildBundles [ '.bin', 'caw', 'color', 'got', 'nan', 'semver', 'tar' ]
4505 info install sharp@0.18.2
4506 verbose unsafe-perm in lifecycle true
4507 info sharp@0.18.2 Failed to exec install script
4508 verbose unlock done using /home/myusername/.npm/_locks/sharp-724c992e50a0ae1d.lock for /home/myusername/BackstopJS/node_modules/sharp
4509 verbose stack Error: sharp@0.18.2 install: node-gyp rebuild
4509 verbose stack Exit status 1
4509 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:217:16)
4509 verbose stack at emitTwo (events.js:87:13)
4509 verbose stack at EventEmitter.emit (events.js:172:7)
4509 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
4509 verbose stack at emitTwo (events.js:87:13)
4509 verbose stack at ChildProcess.emit (events.js:172:7)
4509 verbose stack at maybeClose (internal/child_process.js:862:16)
4509 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
4510 verbose pkgid sharp@0.18.2
4511 verbose cwd /home/myusername/BackstopJS
4512 error Linux 4.9.17-8.31.amzn1.x86_64
4513 error argv "/usr/bin/node" "/usr/bin/npm" "install"
4514 error node v4.8.4
4515 error npm v2.15.11
4516 error code ELIFECYCLE
4517 error sharp@0.18.2 install: node-gyp rebuild
4517 error Exit status 1
4518 error Failed at the sharp@0.18.2 install script 'node-gyp rebuild'.
4518 error This is most likely a problem with the sharp package,
4518 error not with npm itself.
4518 error Tell the author that this fails on your system:

Primajin · 2017-07-25T08:58:26Z

@kiran-redhat I also experienced that from time to time on mac. The problem here is from time to time - so sometimes after rerunning it it went through. Very weird behaviour.

kiran-redhat · 2017-07-27T04:54:20Z

Looks like Amazon Linux AMI doesn't have gcc-c++, sharp install fine after 'sudo yum install gcc-c++'.

laubsauger · 2017-07-28T11:59:22Z

Has anybody noticed that backstop using chromy is taking about 40% longer to execute than the exact same config using phantomjs?
This is the case for me with a single scenario and a single viewport but also with multiple scenarios on multiple viewports. Since chrome-headless can work on the different viewports in parallel i was hoping for quite the performance boost.
No selector or selectorexpansion was used.

Also passing of flags to chromy does not seem to work properly - or i'm doing something wrong 😄
I tried passing engineFlags: ["--ignore-certificate-errors"] and hostFlags: ["--ignore-certificate-errors"]as global config and as scenario-specific config. But neither didn't seem to work. (one of these should be the replacement for casperFlags or not?)
Not sure if chromy or backstop related. As a workaround i'm calling chromy.ignoreCertificateErrors(); in a global onBefore-script.

btw @garris thank's a lot for pushing the chrome-headless integration 👍
I was close to rolling my own and am really glad i didn't start yet

garris · 2017-07-28T13:31:15Z

@laubsauger thanks for testing this version! Yes. Totally noticed. At least some of it is related to #480. Working on it.

Also, please file a ticket for the flags -- probably a bug in there.

Cheers!

garris · 2017-07-28T14:07:08Z

Just to be clear -- it looks like the slowdown is 1) chrome launch time, and 2) per selector capturing.

The chrome option is faster if you have a test with many scenarios each having one selector. Because, even though boot time is slower, they happen in parallel. But, obviously, I am hoping we can do much better.

garris · 2017-08-01T11:10:53Z

@laubsauger #480 has been fixed and @daveaspinall has reported a very significant speed increase. Please retest at your earliest convenience -- would like to know if your issue is addressed also. Thanks!

garris · 2017-08-01T11:15:28Z

Note: please install the latest backstopjs 3.0.6+ and the latest chrome canary 60+. The hostFlags issue is also fixed.

garris · 2017-08-02T05:52:08Z

AS OF 3.0.7 ALL FEATURES ARE SUPPORTED WHEN USING CHROMY OPTION.

garris · 2017-08-02T06:16:10Z

Next steps:

update travis test UPDATE TRAVIS FOR v3.x.x [HELP WANTED] #485
merge to master MERGE 3.x.x to master #486

HELP WANTED! ^^^

djskinner · 2017-08-02T08:59:24Z

Just tried this out and can report everything is working as expected. My config is very simple but the visual output is better (Phantom seemed to struggled with some bits). Anecdotally I would say it runs faster too. Thanks for the effort, you managed to turn this around very quickly!

laubsauger · 2017-08-02T09:00:39Z

@garris Nice.
Unfortunately, since updating (backstop307, chromy403, chrome60) i can't seem to get a clean test run with my scenarios anymore. I can see in the remote debug window that there is nothing really rendered. I'm on CentOS 7.

~~A clean backstop init config seems to work though. So i guess it's something with my environment, chromy scripts or config that broke due to the update~~ - need to look into it later.
update: The default scenario created by backstop init uses browser: ["chrome"] that's why it worked earlier. if i change it to browser: ["chromy"] it won't work either (blank/white page being rendered)
update 2: only seems to happen when debugWindow: true
update 3: nvm. seems somewhat random and i strongly suggest it's something with my machine / os setup

edit: opened Issue with Chromy regarding debugWindow OnetapInc/chromy#53

josh-wilson-sociomantic · 2017-08-02T14:12:08Z

Hmm, I have a set of scenarios that pass individually, but when I run them together (even just 9 scenarios), backstop hangs (two chrome instances never close when I run all tests). So tests/comparison etc is never run. I haven't been able to pin this down to anything specific. (There's some Chromy selector errors, but it still takes shots and these scenarios pass when run on their own...).

Anyone else come up against this?

Im on macosx, node 8.1.4, chrome 60, backstopjs 3.0.7.

Happy to debug if anyone has any pointers as to where to start.

josh-wilson-sociomantic · 2017-08-02T14:57:00Z

Okay, left it running even longer:

(node:74325) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: connect ETIMEDOUT 127.0.0.1:9228 So the browser instance is timing out, but backstop isn't picking it up (I think)

Setting chromy to be viewable I can see the last windows don't progress to a url at all... (digging)

garris · 2017-08-02T17:04:23Z

@josh-wilson-sociomantic @laubsauger @djskinner
Thanks for the bug reports everyone! Would you guys please create new issues for these?

Also, please download and run the backstop test here... https://github.com/garris/backstop-feature-tests -- please include the summary at the end. (with the perf times) e.g. ...

      compare | OK: requireSameDimensions sanity_test_requireSameDimensions_0_body_1_square.png
       report | Test completed...
       report | 92 Passed
       report | 10 Failed
       report | Writing browser report
       report | Browser reported copied
       report | Copied configuration to: /Users/gshipon/Desktop/backstop test/backstop_data/html_report/config.js
      COMMAND | Executing core for `openReport`
   openReport | Opening report.
      COMMAND | Command `openReport` sucessfully executed in [0.077s]
       report | *** Mismatch errors found ***
       report | For a detailed report run `backstop openReport`

      COMMAND | Command `report` ended with an error after [10.25s]
      COMMAND | Error: Mismatch errors found.
                    at /usr/local/lib/node_modules/backstopjs/core/command/report.js:113:17
                    at <anonymous>
                    at process._tickCallback (internal/process/next_tick.js:169:7)
      COMMAND | Command `test` ended with an error after [53.673s]
      COMMAND | Error: Mismatch errors found.
                    at /usr/local/lib/node_modules/backstopjs/core/command/report.js:113:17
                    at <anonymous>
                    at process._tickCallback (internal/process/next_tick.js:169:7)

garris · 2017-08-02T17:10:06Z

@laubsauger

setting browser === "chrom" || "chromy" || "chrome" will all fire up chromy.
I have also noticed that using debugWindow: true messes everything up -- would you mind filing a ticket for that?
nvm is great -- but sometimes causes unexplained weird things to happen. Don't know what to tell you there.

garris · 2017-08-02T17:13:25Z

@josh-wilson-sociomantic the file where the magic happens is runChromy.js Perhaps try running smaller sets/combinations of your scenarios until you find the one guy that's crashing the system. Perhaps some async process is failing and that one chrome instance is preventing the backstop from continuing?

josh-wilson-sociomantic · 2017-08-02T17:19:40Z

Doesn't seem t be any specific test, sadly. Just 10-12+ tests running and it happens.

Perhaps some async process is failing and that one chrome instance is preventing the backstop from continuing?

@garris yeh,that's what I was thinking. Digging in runChromy now and it seems like one or two instances of Chromy open, but maybe after goto has already been called on it?

I started digging up in createBitmaps, and the only thing there could be p-map passing them on before they're ready, though I doubt that.

I wont be back on this machine for a few days, but I'll be digging in more when I can. Thanks, @garris 👍

patriciamarchand · 2017-08-02T17:41:03Z

Super I realy need to migrate to Chrome my tests in the near future. I finally managed to install version 3.0.7 but I hit some problems during the process.

The Sharp module does not want to install properly. The first error was related to SDK windows version. So I installed the required version 8.1 . https://developer.microsoft.com/en-us/windows/downloads/windows-8-1-sdk

After that, I still had an issue with the same module Sharp :
TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified. ...\sharp\build\libvips-cpp.vcxproj.

I found this issue (lovell/sharp#341) and follow the solution "…manually installed Visual C++. https://msdn.microsoft.com/en-IN/library/60k1461a.aspx"

I post it if it could help someone.

garris · 2017-08-03T03:12:38Z

@josh-wilson-sociomantic thanks for taking a look at it. Just for a sanity check -- if you get a chance -- please download and run the test in this project. Please let me know if it runs as expected. And also -- if you're able to share your scenarios and project I would take a look at that. Please open a new ticket for this if you find more info.

dotneet · 2017-08-03T05:43:55Z

@patriciamarchand
Chromy uses sharp to resize or clip an image but Chrome61 has a feature to achieve it without sharp. So the dependency will be removed after Chrome61 is released.

mirzazeyrek · 2017-08-03T09:01:22Z

On ubuntu 16.04 with node 7.2 latest released chrome default tests are working fine.

But my previous tests have some issues.

garris · 2017-08-04T01:40:47Z

@mirzazeyrek thank you for testing! please feel free to open a new ticket for your previous tests. I would like to understand where we need improvements. Cheers.

sattaman · 2017-08-04T08:10:49Z

I've got an error running tests, I've added here , although maybe it should have been in this repo ? OnetapInc/chromy#45

josh-wilson-sociomantic · 2017-08-07T14:50:57Z

@garris I'm happy to say, I found a Chrome instance that was lurking and seemed to be blocking a port. Once I killed the process, everything has been running smoothly.

I've no idea what caused it to block/hang or if it was my normal chrome having done something there...

For now seems good, and I'm keeping an eye for the problem, if it happens again I should be able to glean something more useful. 👍 (but i hope it doesn't :P )

garris · 2017-08-07T16:01:34Z

@josh-wilson-sociomantic

Hey great -- thanks for following up and letting me know! cheers, GS

kensoh · 2017-08-11T02:29:21Z

@garris , @dotneet and guys, just dropping by to say a huge CONGRATS on bringing headless chrome to production! I think this is the first project I see moving from older frameworks to headless chrome, and successfully 😄

I don't use BackstopJS but is an active user of CasperJS for couple of years. Had previously spoken to Chromy creator Shinji and I really second what Garris said. I especially like the clean and rapidly extending API and his fast rate of iteration putting features into prod so fast.

Sorry for posting and not really adding any contribution to this thread. Just can't contain my excitement that Garris and Shinji pulled this off so fast.

garris · 2017-08-12T10:13:09Z

Thanks @kensoh!

lancetharper · 2017-08-17T20:35:38Z

Looks like attribute selectors no longer work? Not sure if this belongs here or in chromy though.

works:
selectors: [ '.test' ]

doesn't work:
selectors: [ "[data-backstop='test']" ]

garris · 2017-08-17T20:37:37Z

@lancetharper Thanks for testing! So, attribute selectors still work using the engine: "phantom" option correct? Just not with chrome option?

lancetharper · 2017-08-17T20:40:35Z

@garris correct.

chrome runs MUCH faster though so I'm very excited to see this version released!

edit:
Issue for chromy (OnetapInc/chromy#60)

garris · 2017-08-17T20:43:36Z

@lancetharper Great to hear!!! Yes, some of my tests are running at double speed...

So, please file this over on the Chromy repo. @dotneet is really amazing with fixes like these.

Cheers!

garris · 2017-08-18T17:16:55Z

CLOSED BY 0535303

garris · 2017-08-18T17:18:18Z

Chrome headless support is now on master.

THANK YOU EVERYONE FOR YOUR SUPPORT!

devm87 · 2017-11-13T08:52:27Z

HI guys, I was wondering if someone could help me with the error I am facing below. I've tried updating my Backstop JS to Chrome headless but can't seem to install using the command below, is this correct?
Many thanks,

D:\AEM_BACKSTOPJS_SMOKE_TESTS>npm install -g backstopjs@beta
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\
node_modules\npm\bin\npm-cli.js" "install" "-g" "backstopjs@beta"
npm ERR! node v6.9.5
npm ERR! npm v3.10.10
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! syscall getaddrinfo

npm ERR! getaddrinfo EAI_AGAIN registry.npmjs.org:443
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! D:\AEM_BACKSTOPJS_SMOKE_TESTS\npm-debug.log

D:\AEM_BACKSTOPJS_SMOKE_TESTS>

Primajin · 2017-11-13T10:21:54Z

According to http://www.codingdefined.com/2015/06/nodejs-error-errno-eaiagain.html this is a problem with your internet connection or proxy setting. I am using the Microsoft Ubuntu Shell on Windows and not node on Windows directly. Does it work when you install other nom modules or is it really only that single one?

devm87 · 2017-11-13T10:42:54Z

Thanks for replying so quickly @Primajin I have installed npm modules before which has worked okay. In this case, I also logged into cmd using an admin user but to no avail. I'll check out on the proxy settings though and rule out the fact that the proxy is an issue :)

devm87 · 2017-11-14T09:22:46Z

Hi @Primajin I spoke to our Network team who said there may not be able to enable/modify our proxy settings in order to run the test below. I tried running the tests from home (using home Wifi) instead of work and came up with a separate error. Any ideas what might be causing this?

Many thanks,

D:\AEM_BACKSTOPJS_SMOKE_TESTS\backstopjs-smoke-tests>npm install -g backstopjs
npm ERR! registry error parsing json
npm ERR! registry error parsing json
npm ERR! registry error parsing json
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @types/node@6.0.66 (node_modules\backstopjs\node_modules\chrome-launcher\node_modules@types\node):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Unexpected token < in JSON at position 0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: <title>404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)</title>
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:

404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

npm WARN optional SKIPPING OPTIONAL DEPENDENCY:

Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: @types/mkdirp@^0.3.29 (node_modules\backstopjs\node_modules\chrome-launcher\node_modules@types\mkdirp):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Unexpected token < in JSON at position 0
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: <title>404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)</title>
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:

404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

npm WARN optional SKIPPING OPTIONAL DEPENDENCY:

Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm WARN optional SKIPPING OPTIONAL DEPENDENCY:
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "backstopjs"
npm ERR! node v6.9.5
npm ERR! npm v3.10.10

npm ERR! Unexpected token < in JSON at position 0
npm ERR!
npm ERR!
npm ERR! <title>404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)</title>
npm ERR!
npm ERR!
npm ERR!
npm ERR!
npm ERR!
npm ERR!
npm ERR!
npm ERR!
npm ERR!

404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

npm ERR!

Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

npm ERR!
npm ERR!
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! D:\AEM_BACKSTOPJS_SMOKE_TESTS\backstopjs-smoke-tests\npm-debug.log

D:\AEM_BACKSTOPJS_SMOKE_TESTS\backstopjs-smoke-tests>

Primajin · 2017-11-14T09:40:01Z

@devm87 Please open an issue ticket here as this conversation will ping all the 15 participants in this thread.

So far I don't have a ready-to-use solution yet but we can discuss better on your new ticket than creating noise in here.

garris mentioned this issue Jul 20, 2017

CHROME HEADLESS support -- in progress #454

Closed

daveaspinall mentioned this issue Jul 21, 2017

Chromy engine runs slow with scenarios containing many selectors #480

Closed

josh-wilson-sociomantic mentioned this issue Aug 9, 2017

Backstop instantiates Chrome in main app instance #491

Closed

laubsauger mentioned this issue Aug 11, 2017

Rendering broken when using non-headless mode {visible: true} OnetapInc/chromy#53

Closed

garris mentioned this issue Aug 17, 2017

Is Sharp still a dependency? OnetapInc/chromy#59

Closed

garris closed this as completed Aug 18, 2017

garris mentioned this issue Aug 21, 2017

Install on Windows fails - Prior to new release it installed without error #499

Closed

BACKSTOP CHROME-HEADLESS BETA VERSION IS HERE! #479

BACKSTOP CHROME-HEADLESS BETA VERSION IS HERE! #479

Comments

garris commented Jul 20, 2017 • edited Loading

daveaspinall commented Jul 20, 2017

Primajin commented Jul 20, 2017

mirzazeyrek commented Jul 20, 2017 • edited Loading

garris commented Jul 20, 2017

daveaspinall commented Jul 20, 2017

garris commented Jul 20, 2017

garris commented Jul 20, 2017

klausbayrhammer commented Jul 20, 2017

kiran-redhat commented Jul 25, 2017 • edited Loading

Primajin commented Jul 25, 2017

kiran-redhat commented Jul 27, 2017

laubsauger commented Jul 28, 2017 • edited Loading

garris commented Jul 28, 2017

garris commented Jul 28, 2017

garris commented Aug 1, 2017

garris commented Aug 1, 2017

garris commented Aug 2, 2017

garris commented Aug 2, 2017

djskinner commented Aug 2, 2017

laubsauger commented Aug 2, 2017 • edited Loading

josh-wilson-sociomantic commented Aug 2, 2017 • edited Loading

josh-wilson-sociomantic commented Aug 2, 2017 • edited Loading

garris commented Aug 2, 2017

garris commented Aug 2, 2017

garris commented Aug 2, 2017

josh-wilson-sociomantic commented Aug 2, 2017 • edited Loading

patriciamarchand commented Aug 2, 2017

garris commented Aug 3, 2017

dotneet commented Aug 3, 2017

mirzazeyrek commented Aug 3, 2017

garris commented Aug 4, 2017

sattaman commented Aug 4, 2017

josh-wilson-sociomantic commented Aug 7, 2017

garris commented Aug 7, 2017

kensoh commented Aug 11, 2017

garris commented Aug 12, 2017

lancetharper commented Aug 17, 2017

garris commented Aug 17, 2017

lancetharper commented Aug 17, 2017 • edited Loading

garris commented Aug 17, 2017

garris commented Aug 18, 2017

garris commented Aug 18, 2017

devm87 commented Nov 13, 2017

Primajin commented Nov 13, 2017

devm87 commented Nov 13, 2017

devm87 commented Nov 14, 2017

404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

404 - Request is serviced by NPM metadata service, remote access not needed from DefaultNpmProxyRepository(id=npmjs)

Primajin commented Nov 14, 2017

garris commented Jul 20, 2017 •

edited

Loading

mirzazeyrek commented Jul 20, 2017 •

edited

Loading

kiran-redhat commented Jul 25, 2017 •

edited

Loading

laubsauger commented Jul 28, 2017 •

edited

Loading

laubsauger commented Aug 2, 2017 •

edited

Loading

josh-wilson-sociomantic commented Aug 2, 2017 •

edited

Loading

josh-wilson-sociomantic commented Aug 2, 2017 •

edited

Loading

josh-wilson-sociomantic commented Aug 2, 2017 •

edited

Loading

lancetharper commented Aug 17, 2017 •

edited

Loading