|
|
| (12 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | [[Category:Peerix]] | + | [[w:Test-Driven Development|Test-Driven Development]] is a [[w:software development|software development]] technique consisting of short iterations where new [[w:test case|test case]]s covering the desired improvement or new functionality are written first, then the production code necessary to pass the tests is implemented, and finally the software is [[w:Refactor|refactored]] to accommodate changes. The availability of tests before actual development ensures rapid feedback after any change. |
| − | =Tests for [[Live CD]]=
| + | Practitioners emphasize that test-driven development is a [[w:Software engineering|method of designing software]], not merely a method of testing. |
| − | *Spins up
| |
| − | *ISOLinux bootloader runs
| |
| − | *Kernel runs
| |
| − | *Framebuffer active
| |
| − | *Interactive console
| |
| | | | |
| − | == Boots and displays image on: ==
| + | Test-Driven Development began to receive publicity in the early twenty-first century as an aspect of [[w:Extreme Programming|Extreme Programming]], but more recently is creating more general interest in its own right. |
| − | *Toshiba Satellite A10 (Celery 2.19GHz) --[[User:Nad|Nad]] 03:03, 13 Dec 2006 (NZST)
| |
| − | *Compaq Evo (P4 1.6GHz) --[[User:Nad|Nad]] 03:03, 13 Dec 2006 (NZST)
| |
| − | *Compaq D510/D530 --[[User:Rob|Rob]] 03:49, 13 Dec 2006 (NZST)
| |
| − | *Dell Precision 390 Dual core --[[User:Rob|Rob]] 03:49, 13 Dec 2006 (NZST)
| |
| − | *iMac 20" Intel 2.19Ghz Dual Core - see [[Peerix on Intel Macs]] --[[User:Rob|Rob]] 03:49, 13 Dec 2006 (NZST)
| |
| − | *Compaq Armada E500 (P3 450MHz) --[[User:Nad|Nad]] 03:58, 13 Dec 2006 (NZST)
| |
| − | *Asus A6J Laptop T2400 Dual core (? 1.83Ghz) --[[User:Milan|Milan]] 04:33, 13 Dec 2006 (NZST)
| |
| − | *Compaq Deskpro EN (P3 800MHz)
| |
| − | :Booted, but couldn't obtain video mode (I think the video card has too little RAM) --[[User:Nad|Nad]] 04:37, 13 Dec 2006 (NZST)
| |
| − | ::Probably running into the 4MB video memory threshold - it's hard to choose the best [[VESA mode numbers|VESA mode number]]. --[[User:Rob|Rob]] 05:43, 13 Dec 2006 (NZST)
| |
| − | ::There is a syslinux ''comboot'' program in the examples in the syslinux source tree that examines the bios and displays the video modes available. This program could be used to make an intelegent decision about what mode to choose. --[[User:Rob|Rob]] 20:06, 13 Dec 2006 (NZST)
| |
| − | *Dell Optiplex GX620 P D 3.2GHz, very slow to display image --[[User:Phalseid|Phalseid]] 15:04, 13 Dec 2006 (NZST)
| |
| − | *IBM Thinkpad 1.83 GHz Intel Duo--[[User:Phalseid|Phalseid]] 15:04, 13 Dec 2006 (NZST)
| |
| − | *Gateway M255 E 1.66 GHz --[[User:Phalseid|Phalseid]] 15:04, 13 Dec 2006 (NZST)
| |
| − | *Mac G5 -pending answer to this question: will i be able to remove the CD?- --[[User:Phalseid|Phalseid]] 15:10, 13 Dec 2006 (NZST)
| |
| − | :I think you hace to hold down C to boot from CD, so to remove CD just reboot without C and eject from OSX like usual --[[User:Nad|Nad]] 18:38, 13 Dec 2006 (NZST)
| |
| − | ::Remember it's built for Intel only that this stage. So it won't run on G3/G4/G5 yet. --[[User:Rob|Rob]] 20:08, 13 Dec 2006 (NZST)
| |
| − | :::thought that this g5 is intel, but it did not boot... --[[User:Phalseid|Phalseid]] 22:31, 13 Dec 2006 (NZST)
| |
| | | | |
| − | == Questions ==
| + | Along with other techniques, the concept can also be applied to the improvement and removal of [[w:software bug|software defects]] from legacy code that was not developed in this way. |
| − | On all my tests there's been garbage coming up for a second or so before the HAL image - this garbage I think is supposed to be a linux penguin and console text. --[[User:Nad|Nad]] 04:37, 13 Dec 2006 (NZST)
| + | |
| − | :Yes it is a palette corupted penguin. And yes it is totally normal. I tried to customise the logo but ended up doing something to it. Better would be no logos at all. --[[User:Rob|Rob]] 05:41, 13 Dec 2006 (NZST)
| + | Test-driven development requires that an [[w:test automation|automated unit test]], defining requirements of the code, is written before each aspect of the code itself. These tests contain [[w:Assertion (computing)|assertions]] that are either true or false. Running the tests gives rapid confirmation of correct behaviour as the code evolves and is [[w:Refactoring|refactored]]. Testing frameworks based on the [[w:xUnit|xUnit]] concept (see the [[w:list of unit testing frameworks|list of unit testing frameworks]] for an exhaustive list) provide a mechanism for creating and running sets of automated test cases. |
| − | http://pc.itek.cz/k_54-Pametove-karty-USB-flash-disky/img-shop/full/RAM2080.jpg
| + | |
| − | *"Error: Specified CD-ROM disk or image file is neither ISOLinux-based nor floppy emulation mode bootable CD-ROM; thus it cannot be converted", trying to convert flash drive on XP using 3rd party software called flashboot. I have a hundred blank cd's at work, and none here. will try again tomrrow --[[User:Phalseid|Phalseid]] 07:22, 13 Dec 2006 (NZST)
| + | == See also == |
| − | :It's better to use an image that is designed to work on USB. There are some subtle differences between ISO9660 (cdrom) and USB format. USB installation from a host OS is tricky because it depends on windows. My thought was to include a USB installer in the CDROM distribution. You boot with CD then use that OS to install on a USB. Remove the CD, plug in the USB then reboot, this time booting fromm USB. --[[User:Rob|Rob]] 08:14, 13 Dec 2006 (NZST)
| + | *http://www.lastcraft.com/first_test_tutorial.php |
| − | ::Also, that error is incorrect. The image ''is'' ISOLinux-based. I wonder what assumptions the software is making in this case. --[[User:Rob|Rob]] 08:16, 13 Dec 2006 (NZST) | + | *[[w:JUnit]] |
| − | :::I emailed their support to see what is up. --[[User:Phalseid|Phalseid]] 02:41, 14 Dec 2006 (NZST)
| + | *[[w:Unit testing]] |
| | + | *[[Selenium]] |
Test-Driven Development is a software development technique consisting of short iterations where new test cases covering the desired improvement or new functionality are written first, then the production code necessary to pass the tests is implemented, and finally the software is refactored to accommodate changes. The availability of tests before actual development ensures rapid feedback after any change.
Practitioners emphasize that test-driven development is a method of designing software, not merely a method of testing.
Test-Driven Development began to receive publicity in the early twenty-first century as an aspect of Extreme Programming, but more recently is creating more general interest in its own right.
Along with other techniques, the concept can also be applied to the improvement and removal of software defects from legacy code that was not developed in this way.
Test-driven development requires that an automated unit test, defining requirements of the code, is written before each aspect of the code itself. These tests contain assertions that are either true or false. Running the tests gives rapid confirmation of correct behaviour as the code evolves and is refactored. Testing frameworks based on the xUnit concept (see the list of unit testing frameworks for an exhaustive list) provide a mechanism for creating and running sets of automated test cases.
See also
