[8412] in athena10
Re: [Debathena] #588: automated install tests
daemon@ATHENA.MIT.EDU (Debathena Trac)
Sat Sep 10 15:03:12 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 19:03:03 -0000
Reply-To:
Message-ID: <052.68001256ceaf21fa2190ce7a6f8c30e6@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 kaduk):
Replying to [comment:6 jrjarvis]:
>
>
> 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.
>
I feel confident we can get a test account (or just use an existing one,
really).
> 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.
I don't think that an init script would give much utility other than
confirming that packages installed correctly (which your setup already
does, I think?).
Ideally we could somehow script waiting for the reboot and logging in with
stored (test account) credentials, and run a testing script from a well-
known location.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/588#comment:7>Debathena <http://debathena.mit.edu/>MIT Debathena Project
