https://sourceforge.net/p/cut/feature-requests/2007-10-14T15:20:55ZRecent changes to feature-requests2007-10-14T15:20:55Z2007-10-14T15:20:55ZJan Hudechttps://sourceforge.net/u/bulbjh/https://sourceforge.net7966903607733b21e8b8e30cdb65b1639a5b6579

<div class="markdown_content"><p>The __CUT_BRINGUP/__CUT_TEARDOWN funcions would be more useful, if they were ran around each test. That way they could be used to set up a clean environment for each test and clean it up afterwards.</p> <p>The current way every test function must clean up after itself (or at the begining clean up after the previous), which makes things a little more complicated.</p> <p>Note, that C++, Java, Python etc. unit-test tools do run their setUp and tearDown methods around each test.</p></div>

2004-09-27T21:26:22Z2004-09-27T21:26:22ZTrevor Crofthttps://sourceforge.net/u/trevorcroft/https://sourceforge.neta61d372dc29c9f5d4433f253232e26930796fbe0

<div class="markdown_content"><p>I have integrated cut into my MSVC++ project.</p> <p>MSVC++ automatically generates the code using cutgen,<br /> and then runs the resulting executable and reports errors.</p> <p>If you'd like the workspaces and project files please<br /> email tbcroft at msn dot com</p> <p>Right now the files are very specific to my environment<br /> but I will tweak them so they will work generically if<br /> there is interest in this.</p></div>