http://www.nicollet.net/2009/08/easier-unit-tests/ Everyone Loves Me Sat, 11 Feb 2012 18:59:19 +0000 hourly 1 http://wordpress.org/?v= http://www.nicollet.net/2009/08/easier-unit-tests/comment-page-1/#comment-11425 Victor Nicollet Wed, 19 Aug 2009 15:21:17 +0000 http://www.nicollet.net/?p=1099#comment-11425 I think I would go for a "run the code in a fully initialized environment", just like in PHP: all the main dependencies are already loaded when the code is executed, which means that most code is available. Having to set up your environment for testing out stuff would turn out to be quite annoying, since the more complex interactions usually require a lot of things to be initialized and running... I think I would go for a “run the code in a fully initialized environment”, just like in PHP: all the main dependencies are already loaded when the code is executed, which means that most code is available. Having to set up your environment for testing out stuff would turn out to be quite annoying, since the more complex interactions usually require a lot of things to be initialized and running…

]]> http://www.nicollet.net/2009/08/easier-unit-tests/comment-page-1/#comment-11367 Joe Venzon Tue, 18 Aug 2009 20:16:14 +0000 http://www.nicollet.net/?p=1099#comment-11367 I think it'd be interesting to apply something similar to C++ development. The user would start the framework UI and set it up to work with a certain set of source files. The user could then repeatedly enter some statement in a text box and hit a "run" button. The UI would then wrap some C++ code for main() around the statement and initiate compilation, linking in the other source files. The UI would then either display the compiler error or, if compilation was successful, run the executable and display the result (the unit under test would need to implement writing to an ostream). If the user clicks the "add case" button, the statement would be appended to a file with the test cases, which could be formatted into a C++ implementation file for the project's unit testing framework, or run directly from the UI. I think it’d be interesting to apply something similar to C++ development. The user would start the framework UI and set it up to work with a certain set of source files. The user could then repeatedly enter some statement in a text box and hit a “run” button. The UI would then wrap some C++ code for main() around the statement and initiate compilation, linking in the other source files. The UI would then either display the compiler error or, if compilation was successful, run the executable and display the result (the unit under test would need to implement writing to an ostream). If the user clicks the “add case” button, the statement would be appended to a file with the test cases, which could be formatted into a C++ implementation file for the project’s unit testing framework, or run directly from the UI.

]]>