Megatest

Artifact [53ec1b1f9d]
Login

Artifact 53ec1b1f9d6d1b2ded3bf3c236beb4ab51df6654:

Wiki page [Plans] by mrwellan on 2018-01-31 13:12:17.
D 2018-01-31T20:12:17.633
L Plans
P 7adc4ca571b62f4b448d3cca826370718ec80e2b
U mrwellan
W 1150
DO NOT EDIT - EDIT "plan" INSTEAD!

In no particular order:

Documentation
  *  Convert to asciidoc
  *  Getting going docs, initial setup
  *  Getting going docs, writing tests

Tests and QA
  *  Release procedure (non-automated tests to run, binary releases)
  *  Whitebox unit tests need to be re-enabled
  *  Inter-area tests, referring to tests in external areas
  *  Performance test

Misc
  *  Binary build for release using chicken deploy mechanism
  *  Microsoft windows port (mostly convert system calls to native posix)
    
Megatest
  *  Refactor, some code has gotten a bit crufty
  *  Log free space in /tmp in the database. Tests often use /tmp and this can help debug problems
  *  Record free memory (account for buffers etc.)
  *  Implement ssh method for calling home (eliminates need for network filesystem).

Dashboard
  *  Add filters to tests
  *  Add visual monitoring of cpu, memory, diskspace etc. for tests
  *  Clean up the threads, reduce to one plus the iup gui thread
  *  Scrolling indicators (currently no visual clue that there <b>are/are not</b> more tests

[Implementation changes]

Z b93c3a4429273545e1ca72b1916726f5