From: SourceForge.net <no...@so...> - 2009-12-01 02:20:39
|
Feature Requests item #434863, was opened at 2001-06-20 18:12 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=365278&aid=434863&group_id=15278 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Vladimir Ritz Bossicard (vbossica) Assigned to: Nobody/Anonymous (nobody) Summary: Plug-in modules Initial Comment: Don't know if this has 1 single chance to be considered but here's my proposition. Goal: design plug-in capability for TestResult listeners. A plug-in will receive the "addFailure", "addTests" evenements from the TestResult object and will deal with it (update an XML tree, write into a file, add statistics...) Advantage: - a better modularity - enable people to write their own listeners and plug them easily via property files - BaseTestRunner don't deal with the dispatch of failures and errors Implementation: - TestResult object doesn't store the errors and failures (the failure() method is used only _once_ and this behaviour can be replaced by the proposed plug-in mechanism) - Only the TestResultListeners store (if they need to) tests, errors and failures. That is what is already done with the Lists and Trees objects. - BaseTestRunner does not implement TestListener anymore but contains a list of TestResultListeners (display tree, list, user-defined via property files...) - Trees and Lists and ProgressBar are TestResultListeners When running a test: - a TestResult instance is created - TestResultListeners are added to the TestResult's listeners by the BaseTestRunner - the TestSuite is run normally ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-12-01 02:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: David Saff (dsaff) Date: 2009-11-16 17:53 Message: This tracker is being shut down. Please move this item to http://github.com/KentBeck/junit/issues ---------------------------------------------------------------------- Comment By: Christopher Eppstein (chriseppstein) Date: 2001-10-27 00:56 Message: Logged In: YES user_id=307090 I think this is a fantastic idea. I find the test result reporting and feedback to be the biggest area of improvement for junit. Having this feature would round it out so that it is available and usable for numerous uses... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=365278&aid=434863&group_id=15278 |