On Wed, Mar 4, 2015 at 6:13 PM, David Malcolm dmalcolm@redhat.com wrote:
From what I can see, you both faithfully followed the instructions in: https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default#How_to_tes... so if it's the intention for the cockpit service to be socket-activated (which sounds sane), I guess that that section needs changing or updating accordingly.
Any ideas what the text of that testcase *ought* to read? Is there some standard testcase rubric for testing a systemd socket-activated service?
Maybe this testcase can be dropped entirely? https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default
Because this one tests actual functionality: https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_basic
On 05.03.2015 02:39, Chris Murphy wrote:
On Wed, Mar 4, 2015 at 6:13 PM, David Malcolm dmalcolm@redhat.com wrote:
From what I can see, you both faithfully followed the instructions in: https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default#How_to_tes... so if it's the intention for the cockpit service to be socket-activated (which sounds sane), I guess that that section needs changing or updating accordingly.
Any ideas what the text of that testcase *ought* to read? Is there some standard testcase rubric for testing a systemd socket-activated service?
Maybe this testcase can be dropped entirely? https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default
The point is test that on the Fedora Server flavor, Cockpit should be working by default, including socket, firewall, etc. This is different from other flavors of Fedora, and so worth testing.
Stef
On Wed, 2015-03-04 at 18:39 -0700, Chris Murphy wrote:
On Wed, Mar 4, 2015 at 6:13 PM, David Malcolm dmalcolm@redhat.com wrote:
From what I can see, you both faithfully followed the instructions in: https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default#How_to_tes...
so if it's the intention for the cockpit service to be socket- activated (which sounds sane), I guess that that section needs changing or updating accordingly.
Any ideas what the text of that testcase *ought* to read? Is there some standard testcase rubric for testing a systemd socket- activated service?
Maybe this testcase can be dropped entirely? https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default
Because this one tests actual functionality: https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_basic
default is Alpha. basic is Beta. (though that may have been a fudge for stuff still being worked on at F21, it might be worth considering just making it a requirement that 'basic functionality' works at Alpha.)
server@lists.fedoraproject.org
-
Adam Williamson -
Chris Murphy -
Stef Walter