Call for testing: jobs-admin

[Ara Pulido]

Hello both!

El 11/08/10 18:18, Greg Beam escribió:
> Hi Jacob,
> 
> Is there any way we could get these Items added to the Desktop-QA-Tracker: 
> http://desktop.qa.ubuntu.com/qatracker/
> 
> I realize these are, for the most part, system levels services, but it would 
> simplify the number of places we need to go to find the testing materal. Maybe 
> add the to the bottom section, under System Services or something?

As you said, desktop.qa.ubuntu.com is more focused on desktop testcases.

But, also, the application is not yet in Ubuntu. Once is in Ubuntu and
used, we can start organizing the testing.

> 
> If the isn't desired, maybe we could create a system level tracker for server 
> and desktop services, so something like services.qa.ubuntu.com and setup the 
> Launchpad / WiKi to follow the same model as ISO-Testing and Desk-To-Application 
> Testing.

The first thing would be to create nice testcases at
http://testcases.qa.ubuntu.com

Any volunteer to create those test cases?

Cheers,
Ara.


> 
> Additionally, test steps would then be present, and those new to the service 
> application, or testing in general would know what they need to test on each 
> service.
> 
> Let me know if you need help with this, as I'd be happy to help out where I can. 
> 
> 
> Greg.
> 
> 
> 
> 
> ----- Original Message ----
> From: Jacob Peddicord <jpeddicord at ubuntu.com>
> To: Steven <stenten at gmail.com>
> Cc: ubuntu-qa at lists.ubuntu.com
> Sent: Tue, August 10, 2010 10:20:21 PM
> Subject: Re: Call for testing: jobs-admin
> 
> On Tue, Aug 10, 2010 at 11:36 PM, Steven <stenten at gmail.com> wrote:
>> I don't mean to sound stupid, but what exactly *is* jobs-admin, and what
>> does it do? What's a job/service? Is it the same as a process (i.e. those
>> shown when running 'top')?
> 
> Perhaps I should have explained it more in my first message: this is,
> essentially, a replacement for services-admin from older Ubuntu
> releases. Jobs (or services, we use the terms interchangeably) are
> system processes that run in the background, keeping your computer
> going. They also control what starts up when the system boots. Example
> jobs: ufw (firewall), ttys (recovery terminals), cups (printing
> services), and crash reporting via apport.
> 
> You can see many jobs in top; most will run as root. These are the
> same thing as services you'd start via the command-line using `sudo
> /etc/init.d/myservice start`, `sudo start myservice`, or `sudo service
> myservice start` (the syntax has changed over the releases).
> 
>> I'd love to help test it, but I'd also like to know what it's supposed to do
>> so I can know if it's working or not :). Some initial test cases would also
>> be nice, but not necessary (playing around is just as much fun when testing
>> software). Thanks!
> 
> Here are some things to try that could be useful in real-world situations:
> 
> * You want to turn off Bluetooth services on your computer to speed up
> boot, since you have no Bluetooth devices: uncheck Bluetooth.
> * You have installed openssh and want to change the port without
> finding the config file where it is located. Find "OpenSSH server" in
> the list and change the port on the right.
> * You want to use PulseAudio as a system service instead of inside a
> desktop session to prevent it from being killed. Find PulseAudio,
> check System mode, hit Apply, then restart the service.
> * You've found a bug with a system service and want to report it:
> select the service, then go to Edit > Report Service Problem.
> 
> There are many, many more things that can be tested. This utility is
> mainly targeted at system administrators and enthusiasts that want to
> tweak their system. Behind it all is jobservice, a powerful framework
> that helps manage these jobs on your system. jobservice can be used by
> other applications to perform certain tasks automatically. By using
> jobs-admin you'll be testing jobservice so we can make it more robust
> for other applications.
> 
> In short: while there are some test cases you can perform, the real
> power behind it can be tested by simply messing around. Pay close
> attention to what you change, however, to make sure you won't regret
> anything. On a default system, you won't be able to change things to
> the point where your system won't boot. This doesn't prevent you from
> breaking networking, printing, or other useful services, though. :)
>