New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some iframe related tests fail in testrunner in full run, but not if run separately #9467

Open
level420 opened this Issue Dec 18, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@level420
Member

level420 commented Dec 18, 2017

All failing tests are somehow iframe related. I suspect that it has something to do with the native iframe "load" event not being fired or not bubbling up to the listeners. The problem is, that if you don't run the test completely but just start each section separately and run them in linear order, starting from "application" to "util" you won't see the tests failing which makes it horrible to debug, as it always needs a refresh and a full run til it breaks.

@level420

This comment has been minimized.

Show comment
Hide comment
@level420

level420 Dec 18, 2017

Member

It should be discussed if it would be possible to split the monolithic travis runs into single sections, to allow running as the tests do not fail this way. At least not if you run them interactively/manually by clicking on the sections and hitting the "run tests" button. This would result in 20 separate runs of testrunner, where we additionally have to move the test classes qx.test.* into qx.test.base to have them in one section.

Member

level420 commented Dec 18, 2017

It should be discussed if it would be possible to split the monolithic travis runs into single sections, to allow running as the tests do not fail this way. At least not if you run them interactively/manually by clicking on the sections and hitting the "run tests" button. This would result in 20 separate runs of testrunner, where we additionally have to move the test classes qx.test.* into qx.test.base to have them in one section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment