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 5 Next »

Test casesMerge existing tests where possible  
Test casesCome up with a naming convention for the tests  
Test casesReview what tests are smoke/daily/weekly (set up weekly clean builds)  
Test casesCome up with a plan for how to track what the tests do (spreadsheet/wiki)How about we define a comment format for the test files and write a little bash script that can trawl the test dirs and extract information into a CSV file. (Having a separate spreadsheet is likely to get out of date easily.) Then use a wiki page to list the test cases that still need writing. 
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??  
  • No labels