Hi,
I wonder if there is a way to run the tests from the command line. I'd like to be able to let Team City run the tests when I commit my source Code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Kelly,
I was a bit confused with this thread (https://sourceforge.net/p/simplyvbunit/discussion/415411/thread/4856977d) and the thread here. Are these 2 different cases? If so how? Sorry if it sounds ridiculous, just trying to understand.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I never wrote a command line test runner as indicated by this thread. Basically it would require a listener to be sent into the SimplyVBUnit framework to build up an appropriate result. In this case for Team City. Returning a result similar to the NUnit command line runner could allow Team City to run and report tests run by the SimplyVBUnit framework, which is separate from the GUI. In the other thread I was talking about a Debug window output class I used to include with older versions of SimplyVBUnit that you could simply build up a TestSuite object and run it in a module method such as Main and pass in a listener (e.g. Debug listener) to generate some kind of output. It would simply output errors to the Debug window as a demonstration. There was nothing in any reasonable sense a command line test runner. Just more along the lines of showing potential for anyone that wished to pursue something for their own needs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I wonder if there is a way to run the tests from the command line. I'd like to be able to let Team City run the tests when I commit my source Code.
Hello,
Unfortunately there is no command line counterpart. The idea has been floating around for a while, but there are currently no plans underway.
Hi Kelly,
I was a bit confused with this thread (https://sourceforge.net/p/simplyvbunit/discussion/415411/thread/4856977d) and the thread here. Are these 2 different cases? If so how? Sorry if it sounds ridiculous, just trying to understand.
Hello,
I never wrote a command line test runner as indicated by this thread. Basically it would require a listener to be sent into the SimplyVBUnit framework to build up an appropriate result. In this case for Team City. Returning a result similar to the NUnit command line runner could allow Team City to run and report tests run by the SimplyVBUnit framework, which is separate from the GUI. In the other thread I was talking about a Debug window output class I used to include with older versions of SimplyVBUnit that you could simply build up a TestSuite object and run it in a module method such as Main and pass in a listener (e.g. Debug listener) to generate some kind of output. It would simply output errors to the Debug window as a demonstration. There was nothing in any reasonable sense a command line test runner. Just more along the lines of showing potential for anyone that wished to pursue something for their own needs.