Megatest

Version 1.39 Mar 26, 2012

• Caching of writes to db in server mode
• Streamlined many writes to not do redundant lookup of test-id *

Version 1.23 Sept 6, 2011

NB// this release changes the db schema. You should make a back up copy of your megatest.db and run “megatest -rebuild-db”

• Run rollup. A group of partial runs can be rolled up into a single run. All records are copied to the newly created run and run deletion has been updated to not delete run directories where there are still references in the database.
• Arbitrary data roll up from tests. From any test data can be rolled up into the database that will then be available when the database is dumped to csv. There is no limit imposed on how much data can be rolled up but the current database used by megatest, sqlite3, will slow down with very large data sets (over 10 meg or so per test).
• A scroll bar mechanism has been added to the dashboard.

Version 1.22

• Waiver propagation. Waivers will carry forward in a series of runs where the keys are the same.
• Rollup of test result value, expected value and tolerance.

Version 1.04 (May 10, 2011)

• Added fine grain deletion of tests

Version 1.03 (May 8, 2011)

• Minimal documentation
• MT_RUNNAME, MT_TEST_NAME, MT_ITEM_INFO variables set for a launched run
• runsdir setting to control where the link tree goes

Version 1.02

• Add path to megatest used at launch to the PATH variable when tests are run.
• max_concurrent_runs to limit how many tests are allowed to run in parallel.
• State and status for tests that fail to call home are set to INCOMPLETE and DEAD/STUCK respectively
• Added -runstep for making running a single step much simpler for the common case. Also supports the -logpro parameter to use a logpro file to process the log.

Version 1.01

• Fixed -m comment param for runs, tests and test steps.
• Added filters to -list-runs for filtering tests and items