-
Notifications
You must be signed in to change notification settings - Fork 82
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
Feature/protractor issue101 #188
Conversation
….ejs Co-authored-by: Matt Raible <[email protected]>
If the tests for this PR have Protractor enabled, and they pass, then I'll approve this PR. |
All the jobs with a client framework runs protractor tests (it is a default). But I don't know why protractor for some entity tests randomly fails (the error is always the same, but occours every time in different react app configured, while in the last time it was in success):
@mraible some suggestions? It seems that sometimes protractor does not find the entity menu navbar (it is strange because it randomly fails in different tests). You can check that with the same commit, runs two builds for the same job, triggered by two events (push on branch, and pull request). But it is weird that one is ok and the other is in failure... |
41114de
to
28757ff
Compare
7bdcef9
to
16dad6b
Compare
16dad6b
to
754517e
Compare
Kudos, SonarCloud Quality Gate passed! |
Hi @mraible, now it's all ok and passed. The issue is caused by some server api that run random errors log in the react client pages: d88ecc4 |
Thanks! |
Integrate protractor e2e client tests with new test integration pipelines, new server api implemented, angular/react routing fix.