![]() ![]() If I can add info to assist in resolving, let me know. Then I decided it's time to split the monster test file back into per-module test files. It took me a full 2 days to get Karma to work at all - asked a lot of (unanswered) questions on SO, tried to get QUnit to work, eventually gave up, pounded my head for a while and managed to get Mocha running, migrated some of my QUnit tests to Mocha, was very happy. I very very highly suspect this is related to RequireJS. If I add a second fooSpec.js file in the watched directory, even if it contains no tests, the browser hangs always after first run. That is, if all my tests are in a single file, it works fine. I've just been bit by this, and can reliably reproduce or not by having more than one testSpec.js file. So it's kind of workaround, not a solution, but it should at least help you to get unstuck. Setting jasmine.DEFAULT_UPDATE_INTERVAL = 0 means disabling this feature. For some reason, this setTimeout is never fired and therefore it hangs (sometimes it does fire). It's this code where Jasmine does setTimeout to schedule running next specs (after browser renders). Don't have time to dig into it now, but would be super awesome, if somebody could look into it. Because this setTimeout, Jasmine gives the browser a chance to render.įor some reason, sometimes this setTimeout never fires back. if you are using html reporter, without this, it would only show the results at the end. Jasmine does setTimeout in this interval, so that the browser can "breath" - eg. Reply to this email directly or view it on GitHub You are running e2e tests, so your problem is more likely something completely different, please create a separate issue.įor those using Jasmine, I looked into 's project and found out something. That every single test works ok when runned alone. Smallest test possible that behaves this way, but there is the possibility I will try to look further to see if there is a pattern, or to make a ![]() If my problem was related to alerts or similar, wouldn't I get this issue (Chrome never returns back from "executing"Įxecuted 40 of 40 tests SUCCESS. (Chrome never returns back from "executing"Įxecuting 8 of 40 tests. It is not that easy to isolate themīecause of the non deterministic behavior, for example:Įxecuting 36 of 40 tests. On Fri, at 7:27 AM, Martin am not really sure it is one test, most probably there are a couple of Share it, I'm just curious what the issue is. ![]() Through a hangout/skypescreen sharing or send me the files, I wouldn't Samsung recommends repairing your device using original Samsung parts at ''authorized Samsung Dealer/Service Center''.Sammla If you can't figure it out. In case ''non-genuine LCD/Touch panel'' is used on your device, similar problem may occur after Android OS Update. ![]() Have you recently change ''device display'' from the service center? Press the power and volume down key simultaneously for few seconds. Please follow the below steps, If the battery is non removable: We recommend to use only ''Samsung-approved accessories'' and using ''unapproved accessories may cause the performance problems'' and malfunctions that are ''not covered by the warranty''. This causes that some areas of the touchscreen may ''not recognize touch'' actions and no respond. When you attach such products to the device, protector film or glass may not be in perfect contact with the device and may get loose from the device. Especially, some ''Samsung-Unapproved protector glasses'' or films only have tapes on the side edges. If you attach a ''screen protector'' or optional accessories to the ''touchscreen'', the touchscreen may not function properly. And please follow the easy troubleshooting steps which might help to solve the issue. We acknowledge your query and apologize for the same. ![]()
0 Comments
Leave a Reply. |