Daily Build and Smoke Test

There are now a set of Daily Builds done on SvenDowideit's vmware server, and the results are uploaded to TWiki MAIN build output and TWiki 4.2.x release branch. The unit test suite is run first, and if there are any failures, the build stops, and an email is sent to the twiki-dev mailing list.

For now, only the latest unit test and build log files are kept, but we could consider keeping them - either inside the autobuild archive, or by using svn..

-- SvenDowideit - 30 Aug 2007

Discussion

The first google search for this gives a nice explanation:

• Google:"daily+build+and+smoke+test"
• Google:daily+build+smoke+test

Topics in Codev:

• AutomatedAddOnsDownload
• AutomatedContribsDownload
• AutomatedPatchesDownload
• AutomatedPluginsDownload
• CodingEnvironment
• CoffeeBreakArchives2004
• KernelBuildScriptDev
• PersonalRoadmapForSvenDowideit
• TWikiDevelopmentStartingKit

-- SamHasler

For PostCairoDevelopmentModel it would be good to have a test something like this:

1. Tests on auto-generated topic (Test web?)
   1. Run a viewTestScript on a generated topic
   2. Run a saveTestScript
   3. Run a previewTestScript
   4. Run an attachScriptTest
   5. Run a searchScriptTest
   6. Run a rdiffScriptTest
   7. Run a statisticsScriptTest
   8. Run a changesScriptTest
   9. Run a renameScriptTest (topic and attachment?)
   10. Run an uploadScriptTest
   11. Run a manageScriptTes
   12. Run a viewfileScriptTest
   13. Run an oopsScriptTest
2. Run unit tests, where they are defined
3. XHTML conformance of a simple page (e.g. WhatIsWikiWiki)
4. XHTML conformance of a complex search page
5. XHTML conformance of TWikiDocumentation

CPAN:Test::Unit is a good candidate for running this test. It will use the TWiki run at the head of the DEVELOP branch, though the test script could run anywhere. It should write the latest test results to a Wiki topic (which should then be WebNotified so people can be alerted, so it would be best if this was on a WebNotify capable server).

-- CrawfordCurrie

the output of a build, install (at http://tinderbox.wbniv.wikihosting.com/cgi-bin/twiki/view.cgi/), and test run are now archived at http://develop.twiki.org/~develop/cgi-bin/view/Tinderbox/

• the build is performed by the KernelBuildScript and TWikiInstallerContrib
• the installation is performed using the install-remote-twiki.pl script from TWikiInstallerContrib; the log of the installation is attached to the results topic
• the results of the TWikiUnitTests are attached to the results topic, and shown in the topic text

-- WillNorris - 03 May 2005

Snipped some done history - Its worth going through the remaining to see if there are any things we still should implement.

On my TODO list are:

1. add perlcritic to prebuild checks
2. add perltidy to prebuild checks to show continued conformance to CodingStandards
3. add memory and performance tests
4. add building of installers where possible

-- SvenDowideit - 31 Jan 2008