QA (public) » openQA Project (public) » openQA Tests (public)

I'm not sure what could this test detect as it doesn't test NIS functionality, at best it's testing UI

Discussed with zluo: The addition to the test plan was initially rejected because we wanted to find a common solution for both SLE and openSUSE (and in the process failed to add it for any ;-) ). I suggest to do the following steps in this order:

• add module to SLE test plan as is
• check module works for SLE using the production NIS instance (nis.suse.de)
• merge this test
• next step: Add NIS server in "supportserver"
• use supportserver in yast2_nis test instead of nis.suse.de
• add yast2_nis for both sle and opensuse

agreed?

that one uses an internal server so that cannot be used for openSUSE. is there a separate issue to improve that?

Since I cannot provide a working support server(using tap device) for multi machine testing. As discussed with okurz we add this simple nis test for sles only. If you know someone can help with tap device, please let me know.

you mean for a test setup on your workstation? I'm sure there's someone among your colleagues who could take a look at the openqa.suse.de workers to duplicate their setup on a test system.

Unfortunately no. I tried so long and the documentation on openQA for tap setup is not really useful.

So commit 81d71f3 makes use of the module which was previously unused. That is very good. Btw, the always latest can be found here. Thank you zluo for this.

Keep in mind that this ticket here focuses on the yast configuration interface even though it uses a nis server. There is still #9900 which @dzedro is working on and is still in progress. I will link these tickets accordingly.

As mentioned in #13252#note-5 the way to go after we now have the module used in SLE is either

• next step: Add NIS server in "supportserver"
• use supportserver in yast2_nis test instead of nis.suse.de
• add yast2_nis for both sle and opensuse

OR

• continue on tests/x11/nis_client.pm and tests/x11/nis_server.pm as started by @dzedro, see #9900

Let's concentrate on one ticket and not duplicate work. We can still later one consolidate on making yast2_nis focus more on the interface and the others on functionality and keep both for SLE as well as openSUSE.