Opened 13 years ago
Last modified 10 years ago
#1093 new enhancement
IZ152: testsuite shall cleanup test global variables after the check
Reported by: | joga | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | testsuite | Version: | current |
Severity: | Keywords: | framework | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=152]
Issue #: 152 Platform: All Reporter: joga (joga) Component: testsuite OS: All Subcomponent: framework Version: current CC: None defined Status: NEW Priority: P3 Resolution: Issue type: ENHANCEMENT Target milestone: milestone 1 Assigned to: issues@testsuite QA Contact: joga URL: * Summary: testsuite shall cleanup test global variables after the check Status whiteboard: Attachments: Issue 152 blocks: Votes for issue 152: Vote for this issue Opened: Fri Oct 19 03:21:00 -0700 2007 ------------------------ Many testsuite tests use global variables to store information during the test run. Sometimes quite large amounts of information are stored there, e.g. monitoring data in the performance/throughput test. The test template (checktree/test_template) foresees to destroy the global variables in the cleanup function, but most tests don't do it yet. A better approach would be to destroy the test global variables automatically in the testsuite framework: - before a check is started, get a list of all global variables (TCL function "info globals") - after the check get the list of all globals, and delete the newly created ones. Once this is done, remove destroying the globals from the tests cleanup functions.
Note: See
TracTickets for help on using
tickets.