[Testing] Automation Scripts

[Joseph A. Feinstein]

Suggestion for a script(s) #2:

Remotely login into each required laptop and edit required 
configuration files (first files to be considered: .xsession in 
/home/olpc and config in /home/olpc/.sugar/default).

Joe
----------
At 12:17 PM 10/13/2008, Mel Chua wrote:
>More generalized: a framework that would let you write scripts like 
>the one Joe described below.
>
>types of actions it would be great to script
>--------------
>* connect to the internet
>* verify connection
>* olpc-update
>* check current build
>* run something in Terminal Activity or in the VT - this would allow 
>you to do all sorts of stuff, like netstat and pwr-log, and hook in 
>other test tools - including gui test tools that can be called from terminal.
>* in order to do the above, it'd help to be able to wget/yum-install 
>packages/scripts on the remote XO, and scp logs back up to somewhere 
>afterwards (this should be doable if you can remotely ssh in as root).
>
>when run, this framework would
>--------------
>* remotely login to every listed laptop
>* run your script
>* report results
>
>-Mel
>
>Joseph A. Feinstein wrote:
>>Reuben,
>>
>>The absolutely first thing that comes to mind: having a script 
>>which (based on a "tester's given" list of laptop names and 
>>parameters of the olpc-update command) will remotely login into 
>>every listed laptop, connect it to the Internet, verify the 
>>connection, start the olpc-update command and (possibly) verify 
>>that the update successfully happened.
>>
>>Joe
>>---------
>>At 05:43 PM 10/10/2008, Reuben K. Caron wrote:
>>>I'd like to think about automation scripts over the break. Please 
>>>let me know what you need and have in mind.
>>>
>>>Thanks,
>>>Reuben
>>>
>>>--
>>>Reuben K. Caron
>>>Country Support Engineer
>>>One Laptop per Child
>>>Mobile: +1-617-230-3893
>>>reuben at laptop.org
>>
>