Skip to content
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

Problem when testing security-sample-shared with TestBench #301

Open
jcgueriaud opened this issue Feb 20, 2017 · 2 comments
Open

Problem when testing security-sample-shared with TestBench #301

jcgueriaud opened this issue Feb 20, 2017 · 2 comments

Comments

@jcgueriaud
Copy link

jcgueriaud commented Feb 20, 2017

I tried to test this application with Vaadin TestBench and I've got this error when I try to go on a secured view.

2017-02-20 16:38:50.003 WARN 5392 --- [o-auto-1-exec-8] com.vaadin.ui.ConnectorTracker : org.vaadin.spring.samples.security.shared.views.AdminView$$EnhancerBySpringCGLIB$$d3aac251(19) claims that com.vaadin.ui.Button(20) is its child, but the child claims org.vaadin.spring.samples.security.shared.views.AdminView(19) is its parent.
2017-02-20 16:38:50.003 WARN 5392 --- [o-auto-1-exec-8] com.vaadin.ui.ConnectorTracker : org.vaadin.spring.samples.security.shared.views.AdminView(19) claims that com.vaadin.ui.CssLayout(12) is its parent, but the parent does not acknowledge the parenthood.
2017-02-20 16:38:50.005 ERROR 5392 --- [o-auto-1-exec-8] com.vaadin.server.DefaultErrorHandler : java.lang.AssertionError: The connector hierarchy is corrupted. Check for missing calls to super.setParent(), super.attach() and super.detach() and that all custom component containers call child.setParent(this) when a child is added and child.setParent(null) when the child is no longer used. See previous log messages for details.

I don't understand what the "real" problem.

I attached the edited security sample shared (you need to copy chromedriver inside the project)

security-sample-shared.zip

@ghost
Copy link

ghost commented Feb 20, 2017

Have you tried to run your tests with disabled JVM Assertions? Surefire runs all tests with -ea flag by default, configure Surefire with <enableAssertions>false</enableAssertions>.

@jcgueriaud
Copy link
Author

Thanks a lot.
It's working if I change my pom.xml.

I don't understand why the connector hierarchy is corrupted but I can run my tests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant