-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Facilitate running tests #38775
Facilitate running tests #38775
Conversation
526fc63
to
670b5c4
Compare
@Hackwar I can skip the ldap tests during the Integration tests if JTEST_LDAP_HOST in the xml config is empty, but I did not implement it because that results in false successful integration tests. |
Hey @tatankat, thanks for this work. I'm going to merge this as soon as possible, however I would ask you to indeed mark the tests as skipped as described here https://phpunit.readthedocs.io/en/9.5/incomplete-and-skipped-tests.html if LDAP tests are not explicitely expected to run. We just have way too many people with no ldap and they should be able to run this as well. Do we have to modify the .drone.yml as well? |
I tried several different ways on how to run the openldap docker image, but none worked. I always get "couldn't connect to authentication service". I'm on windows and used the command you provided in the Readme. I adapted the path to my local one and used both host and bridge network and in the configuration I used the IP address, localhost, openldap and none worked. I'm not a pro with Docker, so maybe you can help me? |
And just when I wrote that above, I got it to work. With the command given in the Readme, you get a local server which you can access with localhost:[port]. @tatankat, if you can mark the tests as skipped if ldap_host is empty, I would mark this as a successfull test. |
@Hackwar Thanks for giving the ldap server a try! I implemented your proposed change and made the documentation a bit more clear. |
@Hackwar do you expect something else from me? Once this is merged, I will be able to:
I don't know how to fix the existing conflict here. The changes in this PR can overwrite the typo fixes done in #39357 as the documentation is completely updated. |
Can you fix the conflicts? |
The integration tests are failing. |
No, they aren't ;) |
We will see... |
Can you fix the conflict here? |
Thank you very much! Will adapt now my unit test pr. |
Summary of Changes
Testing Instructions
Following the READMEs:
Actual result BEFORE applying this Pull Request
You spend a lot of time figuring out how the CIs are doing it and copy the same behavior.
Expected result AFTER applying this Pull Request
It took you less time and maybe even tested on your existing ldap server.
Documentation Changes Required
Point people to these READMEs