AutoTesting

From MorphixWiki

Jump to: navigation, search

varc4t ouacreldels pasdronba

Contents

[edit] Auto Testing

Automation is good - autobuilds are good.

We now have: -

  • CVS to commit
  • Debian packages built using the cvs
  • Autobuild based upon Debian packages


I am thinking about the following: -

[edit] Auto-Testing System

  • Auto Install based on mpmis
  • Complete the following tests :-
    • Autobuilt base + stable mainmod
    • Autobuilt base + autobuilt mainmods
  • Auto Upload
    • dmesg
    • Screen-shots - if X loads
    • Contents - /etc/syconfig/
    • Network Status
    •  ?

[edit] How

[edit] Method 1

Based on mpmis swap between two poor man install

Install 1 - Is the Morphix we are Testing
minimod-auto-test.mod
to save information
to swap over grub to boot install 2
Install 2
Tar up the uploads, upload,
Download new Morphix
Build new iso & poor mans install
To swap over grub to boot install 1

[edit] Method 2

Based up qemu inside a normal install.

Tar up the uploads, upload,
Download new Morphix
Build new iso including
Auto Testing minimods and
Auto-Testing scripts,
Boot option debugmorphix=y
Boot using Qemu - and screen capture (every 2 Seconds ?)
Kill qemu session after 5-10 minutes
Convert Screen-shots to video.
Balance size of video, frames per second, length of video
Also save data as per Method 1

[edit] Pros & Cons

[edit] Method 2 Pros

  • No reboots
  • Video

[edit] Method 2 Cons

  • Not testing real hardware


[edit] Method 1 Pro

  • Testing real hardware

FIELD_MESSAGE_baschira

[edit] To Do

  • Decide on Method 1 of 2
  • Solve problem of only one poor mans working on a pc
    • Poor mans will only use the first poor mans installed, never the second regardless of boot parameters
  • Write minimodule and scripts
  •  ???
  • Profit
Retrieved from "http://www.morphix.org/wiki/index.php/AutoTesting"
Personal tools