restarting tests after completion about tcunit

[sagatowski]

You can ignore a test by simply starting the testname with disabled_. Then you don't need to run the tests that are taking a long time. If this was the problem?

[Aliazzzz]

Nope... The 'problem' is when I develop a new test, I want to run test-drive this tests usually multiple times...

[sagatowski]

I'm not sure I follow then. You only want to re-run the tests that are new, and also without doing a restart of the runtime?
Or is it just that you don't want to restart the runtime, though it's fine that all tests are re-run?

[Aliazzzz]

Bingo!
Re-run the tests that are new, without doing a restart of the runtime. That is what I ment.

The writing and the tuning of a new test, running the test with cold starting the PLC each time gets "tedious" after a full day... I think I inherited a healthy dose of lazyness.

I have a suggestion. Maybe we can think of a feature which alleviates the dev-cycle.
It will save some time and effort as the RUN() command simply runs all testssuites once and only once.
This offcourse is good and should not be altered. However, maybe we can add a new function which can start and restart (run/rerun) a certain testsuite (or predefined testsuites) at will.
RERUN( ptTestSuiteWhichWeWantToRUN, xStart );

The function is offcourse only neccesary in debug cycles.
When writing and testing of tests is done, this code should be replaced with RUN();

I'd love to hear your opinion on this

[sagatowski]

In any case I guess it would be necessary to do a restart of the runtime, if the code is to be altered, no?

What I usually do when I need to re-run test is to simply comment all the test-suites that I know are passing, test the new test-suites, and then uncomment all. Isn't this (in most cases) just as fast as have to create some sort of array with pointers to a test-suite, and make a separate call to them (while re-starting the runtime as well)?

[Aliazzzz]

The usecase requires no coding, just patience ;-)

Closed

[Bulkje]

When I'm writing tests and I don't want to run all the testsuites, I just comment them out. Or disable extendedtestresults in tcunit parameters. Just make sure not to commit it.

[Stevenlawrencehoriba]

I am hitting the same issue, i have lots of tests in the test suite and its crazy trying to debug a test embedded in a testsuite, when you want to debug it and have to re-run, the whole shibang to debug one function. and example of how to go about disbabing 100 tests in set of test suits, without going through every single one. can you just disable a top level suite of tests. an example would help, but to be able to loop the test suite over and over woudl be useful when debugging, with a small delay between test runs which can be configurable. OR coudl i just put a FOR LOOP aroudn the RUN code to continuosly run it?