[8407] in athena10

home help back first fref pref prev next nref lref last post

Re: [Debathena] #588: automated install tests

daemon@ATHENA.MIT.EDU (Debathena Trac)
Fri Sep 9 21:26:13 2011

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: geofft@mit.edu, jrjarvis@mit.edu, jdreed@mit.edu, kaduk@mit.edu
Date: Sat, 10 Sep 2011 01:26:03 -0000
Reply-To: 
Message-ID: <052.94c35ef0986053b61d77684cf4a46de2@mit.edu>
In-Reply-To: <043.3b747147b60146f8f76e26f883c91ed6@mit.edu>
Content-Transfer-Encoding: 8bit

#588: automated install tests--------------------+-------------------------------------------------------
 Reporter:  geofft  |       Owner:  jrjarvis 
     Type:  defect  |      Status:  assigned 
 Priority:  normal  |   Milestone:  Fall 2011
Component:  --      |    Keywords:           
 See_also:          |  
--------------------+-------------------------------------------------------
Comment(by jrjarvis):
 > Well, the big thing would be to test logging in.
 > Off the top of my head, it would also be good to test locker software
 (say, matlab) and some of the athena utilities such as moira and friends,
 maybe discuss or something.
 > Checking that the athinfo queries work as expected would also be good.
 (Do we run anything else other than a fingerd?)
 >

 Anything that requires credentials may be tricky unless we have a test
 account or other approaches to testing software that's run out of a
 locker, logging in, etc.

 The easiest thing to do would be to drop an init script at the end of
 install but I'm not sure how valuable that will be since it will be run
 outside of the chroot environment.  For now I can wait until the reboot
 and make sure it's at the very least alive after the install.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/588#comment:6>Debathena <http://debathena.mit.edu/>MIT Debathena Project

home help back first fref pref prev next nref lref last post