Create nighlty testing server

[GoogleCodeExporter]

*NOTE*

This activity is for mentor only! Students are not expected to contribute to it.

To perform quality assurance of our project it would be nice and fun to have a 
server that performs regular testing.

Such server should do the following tasks e.g. twice a week:
 * Fetch latest SVN
 * Build all modules
 * Run defined set of tests
 * Report results to mailing list 

I, Grigory Rechistov, is the initial owner of this bug and will try to 
implement such a server.

Original issue reported on code.google.com by grigory....@gmail.com on 26 Oct 2010 at 5:56

[GoogleCodeExporter]

The first version of bightly testing routine is deployed on 'maria' Ubuntu 
server. It is cron'ned to be run twice a week.

The details are going to be committed to SVN.

Original comment by grigory....@gmail.com on 30 Oct 2010 at 8:12

• Changed state: Started

[GoogleCodeExporter]

Brought up two virtual servers (in QEMU) with Ubuntu 10.04 with x86_64 and 
x86_32 architectures, set up the required programs, redirected ports for SSH 
access. 

The next steps are:
 # Set up mdsp_test_suite.sh
 # Add twice-a-week schedule to /etc/crontab
 # Create accounts for student access.
 # Set up auto-update of the suite script
 # Test that everything works.

Original comment by grigory....@gmail.com on 3 Nov 2010 at 9:54

[GoogleCodeExporter]

Brought up two VMs, set up testing on these hosts. They are a bit slow but 
function all right.

Original comment by grigory....@gmail.com on 4 Nov 2010 at 5:22

[GoogleCodeExporter]

Two virtual machines are observed to report with mail several times per week.

Imporvement plans:
 # Add possibility to self-update the test script from SVN
 # Add command line arguments to test a particular branch, not the HEAD (to allow students to test their improvements before merging)
 # Make Qemu-script to be FreeBSD services so they are started automtically at every boot.
 # Add a cron job to clean up old SVN working copies from VM hard disk to save space.

Original comment by grigory....@gmail.com on 8 Nov 2010 at 8:32

[GoogleCodeExporter]

Testing of branches is added. 

Working on a tool for self-updating the script.

I also will need to extend the set of tests as  issue is resolved and we can 
test funcsim on simple_test.bin . 

Original comment by grigory....@gmail.com on 16 Nov 2010 at 10:54

[GoogleCodeExporter]

Managed to get the MS VS build and email sending. The Windows testing will be 
less thorough than one for Linux, I guess, because it's harder to write scripts 
for this OS for me. But anyway, I guess Windows targets will get much more of 
manual testing by our project members anyway.

After the final preparations are over the OS image will be deployed on server 
and turned on for sheduled testing.

Original comment by grigory....@gmail.com on 26 Nov 2010 at 6:49

• Added labels: OpSys-Windows

[GoogleCodeExporter]

Having troubles with porting VM disk image from Virtualbox to Qemu. Stupid 
Windows does not have drivers. Though this is fixable.

Original comment by grigory....@gmail.com on 27 Nov 2010 at 9:58

[GoogleCodeExporter]

Seems that Windows cannot be ported from Vbox to Qemu - it losts the disk it is 
installed on! Then I'll bring it up on VirtualBox.

Original comment by grigory....@gmail.com on 2 Dec 2010 at 8:22

[GoogleCodeExporter]

Started VirtualBox headless with Windows XP in it. Redirected port tcp:3389 so 
that the guest can be accessed through RDP. So wo-hoo, Windows regular testing 
is on its way.

The things left to do:
auto-updater
auto-cleaner
startup scripts (2/3 done)
document all of this stuff in our wiki

Original comment by grigory....@gmail.com on 2 Dec 2010 at 10:14

[GoogleCodeExporter]

Implemented auto-updater and auto-cleaner of regular test system both for 
Windows and Linux test bots. Implemented also all the required startup/shutdown 
scripts for bringing up/down VMs at host's boot/shutdown time. Though Windows 
has some problems with it, as usual.

Now I need to test the testing framework. And then - support it :-).

Original comment by grigory....@gmail.com on 6 Dec 2010 at 8:03

[GoogleCodeExporter]

All regular testing VMs are transferred to Ilab host helena.ilab.mipt.ru. Works 
fine.

Original comment by grigory....@gmail.com on 28 Mar 2011 at 6:29

[GoogleCodeExporter]

Test bots are still there (at helena.ilab.mipt.ru) but turned off. Someone has 
to take the effort to maintain them.

Original comment by grigory....@gmail.com on 1 Sep 2011 at 8:44

• Changed state: New