✎ soc:2009:dverkamp:project_plan:start

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Daniel Verkamp: Automated regression testing ======

===== Project Plan =====

==== Summary ====

There is currently no automated way to test gPXE's features. This project would involve implementing an automated regression testing framework to test gPXE's features, both in virtual machines and on real hardware. This would allow gPXE developers to ensure their modifications do not break existing functionality, and it would allow third-party vendors to verify that their particular hardware works with gPXE.

==== Outline ====


The automated testing framework should allow automatic, unattended execution both in virtual machines (qemu, VMware, etc.) and on real hardware.

For tests that require external infrastructure (i.e. servers) to be set up, some kind of automated setup scripts will be provided.

Tests that run in VMs could be parallelizable (for example with make -j) to improve testing speed on more powerful hosts.

Some of the areas that can be tested include:

  - protocol tests
    - download images (of various sizes) from each protocol source and verify their contents (md5sum)
    - possibly time the tests to measure download speed

  - serial console
    - test in qemu with -serial (file)
    - test on real hardware with null modem cable

  - booting
    - linux kernel - supply script that boots some basic kernel with initrd and checks to see if it gets to the login prompt
    - pxe - some basic pxe payload to test (pxelinux?)
    - comboot
    - Windows RIS

  - APIs
    - pxe
    - comboot
    - gdb stub
    - gPXE scripting language

  - driver tests
    - test each virtual device in QEMU, bochs, virtualbox, etc.

  - various memory sizes/layouts (using a VM/emulator)

==== Milestones and Timeline ====

=== Week 3 ===
  - Write 4 detailed test cases and run them manually, documenting the procedure and taking a screenshot of the success condition
    - Linux mkbootfs
    - Windows iSCSI
    - WinPE
    - one other Linux-based test

=== Week 4 ===

  - Finish writing Linux test cases from week 3
  - Write more detailed tests and run them manually, documenting the procedure and success condition
    - Windows RIS (version to be determined)
    - Windows 7 install on iSCSI
    - Possibly more; to be determined

Trace: • mdc • week8 • week2 • aoeboot • rom-o-matic • revised_timeline • abft • httpboot • winnt_iscsi • andytim_todo • less1 • howtos • week9 • opensolaris_iscsi_install • journal • tg3 • dnsmasq • ideas • download • contact