search

atecarlos / protractor-http-mock

A library designed to work alongside Protractor for setting up mocks for your HTTP ajax requests.
MIT License
173 stars 70 forks source link

Amount of mocks loaded breaks Protractor #117

Closed Gbuomprisco closed 7 years ago

Gbuomprisco commented 7 years ago

Sorry for the vagueness of this ticket, it is a very strange issue and I thought I'd post it here regardless.

I am working on a project in which all our tests are using mocks. The amount of mocked data is quite big, and yesterday we got a very strange issue:

Failed
[chrome #01-10]     Failed: Error while running module script httpMock: disconnected: Unable to receive message from renderer
[chrome #01-10]   (Session info: chrome=56.0.2924.87)
[chrome #01-10]   (Driver info: chromedriver=2.26.436382 (70eb799287ce4c2208441fc057053a5b07ceabac),platform=Linux 4.2.0-42-generic x86_64) (WARNING: The server did not provide any stacktrace information)
[chrome #01-10] Command duration or timeout: 95 milliseconds
[chrome #01-10] Build info: version: '2.53.1', revision: 'a36b8b1', time: '2016-06-30 17:37:03'
[chrome #01-10] System info: host: 'railsonfire_aadcd123-37e8-4b76-a0e6-ae9ecb2e3edb_78404b7b9fd4', ip: '127.0.1.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.2.0-42-generic', java.version: '1.7.0_121'
[chrome #01-10] Session ID: 11d37844ad8a85bab91fc81c2e8ff697
[chrome #01-10] Driver info: org.openqa.selenium.chrome.ChromeDriver
[chrome #01-10] Capabilities [{platform=LINUX, acceptSslCerts=true, javascriptEnabled=true, browserName=chrome, chrome={userDataDir=/tmp/.org.chromium.Chromium.TwAEyg, chromedriverVersion=2.26.436382 (70eb799287ce4c2208441fc057053a5b07ceabac)}, networkConnectionEnabled=false, unexpectedAlertBehaviour=, rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, version=56.0.2924.87, pageLoadStrategy=normal, takesHeapSnapshot=true, cssSelectorsEnabled=true, databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, webStorageEnabled=true, nativeEvents=true, hasTouchScreen=false, applicationCacheEnabled=false, takesScreenshot=true}]

At first I thought I'd written some syntax errors in the mocks, but they were fine. So I started removing some mocks, and discovered that by removing (correct) mocks or reducing their size would make it work. Is this a known limit, or this is an isolated event?

atecarlos commented 7 years ago

Hi @Gbuomprisco . I have not seen or heard about this issue before. I would be curious to try it out locally to see if I can reproduce the problem. If you are interested, feel free to post your mocks somewhere I can access it and I can try it out on my side.