Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

AreaSuggestionCommentsStatus
Test casesMerge existing tests where possible  
Test casesSet up weekly clean builds  
Test casesCome up with a plan for how to track what the tests do (spreadsheet/wiki)Bash script developed. Needs some updating though e.g. add a tag for DB/platforms which are disabled. 
EnvironmentAdjust logging settings on FreeBSD so that kernal logs don't show up in syslog resulting in double logging (which messes up the counting of logs as part of a test.....)  
FrameworkIncrease the number of retries on FreeBSD to avoid failures due to the 'ghost' bug in libc. Maybe increase the reporting of re-tries by adding to junit or having a summary line at the end of the console output?  
FrameworkCan we make set up and running of the tests a one step process and then possibly have a "make check" that runs the jenkins tests.  
FrameworkTest with RETRY=0. Would like to use this in the sandbox but seemed to leave some files around that made the next test fail.  
FrameworkNeed a script/tool that can do some consistency checking of the signed zones  
FrameworkUse one copy of the unsigned zone default (don't have a duplicate zone in each test)  
FrameworkMove the xml files into their own directory  
FrameworkCreate functions to handle generic tasks like setting up the environment and starting and stopping the system  
FrameworkCould we script switching between databases rather than having 2 conf.xml files  
FrameworkPerhaps a bit more logging when things go wrong? ("String not found" log message and cat the offending log file)  
JenkinsIs there any way at all to set the tests up so that jenkins displays a matrix of each test case against platform?? Done!
  • No labels