1*4882a593Smuzhiyuntc Testing Suite To-Do list: 2*4882a593Smuzhiyun 3*4882a593Smuzhiyun- Determine what tc features are supported in the kernel. If features are not 4*4882a593Smuzhiyun present, prevent the related categories from running. 5*4882a593Smuzhiyun 6*4882a593Smuzhiyun- Add support for multiple versions of tc to run successively 7*4882a593Smuzhiyun 8*4882a593Smuzhiyun- Improve error messages when tdc aborts its run. Partially done - still 9*4882a593Smuzhiyun need to better handle problems in pre- and post-suite. 10*4882a593Smuzhiyun 11*4882a593Smuzhiyun- Use python logger module for debug/verbose output 12*4882a593Smuzhiyun 13*4882a593Smuzhiyun- Allow tdc to write its results to file. 14*4882a593Smuzhiyun Maybe use python logger module for this too. 15*4882a593Smuzhiyun 16*4882a593Smuzhiyun- A better implementation of the "hooks". Currently, every plugin 17*4882a593Smuzhiyun will attempt to run a function at every hook point. Could be 18*4882a593Smuzhiyun changed so that plugin __init__ methods will register functions to 19*4882a593Smuzhiyun be run in the various predefined times. Then if a plugin does not 20*4882a593Smuzhiyun require action at a specific point, no penalty will be paid for 21*4882a593Smuzhiyun trying to run a function that will do nothing. 22*4882a593Smuzhiyun 23*4882a593Smuzhiyun- Proper exception handling - make an exception class and use it 24*4882a593Smuzhiyun 25*4882a593Smuzhiyun- a TestCase class, for easier testcase handling, searching, comparison 26*4882a593Smuzhiyun 27*4882a593Smuzhiyun- a TestSuite class 28*4882a593Smuzhiyun and a way to configure a test suite, 29*4882a593Smuzhiyun to automate running multiple "test suites" with different requirements 30*4882a593Smuzhiyun 31*4882a593Smuzhiyun- super simple test case example using ls, touch, etc 32