| Issue 22: | implement caching into remotefacade | |
| 1 person starred this issue and may be notified of changes. | Back to list |
right now, the eclipse plugin runs each method one at a time. thus, if a test case has 20 methods, it runs the remote facade 20 times and thus creates 20 objects, running the constructor 20 times, etc. the reason is that it just uses the existing method-level run that has been in mxunit for a while now. however, when running from within eclipse, it's possible that you want to run testcase-level runs repeatedly, and it's a shame that you incur that ugliness with the multiple object creation. So... i can implement a mechanism by which the plugin, at the start of each run, generates a UUID and passes that to the facade. the facade will then, upon first notice of this new UUID, create a new key in an application-level map. it'll construct the testcase object and add it to the map. subsequent calls from the same eclipse run (i.e. coming from the same UUID) will fetch that constructed object and run the appropriate method. at the end of the eclipse run, eclipse will then run a cleanup method on the remotefacade that will remove that key from the cache.
Nov 4, 2007
Project Member
#1
marc.es...@gmail.com
Status:
Fixed
|