Search Project: *:*

 
<< < 1 .. 1494 1495 1496 1497 1498 .. 3647 > >> (Page 1496 of 3647)

Home dhowells wiki (WikiPage)
This is the personal project of dhowells. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-04

wiki Discussion dhowells wiki (Discussion)
Forum for wiki comments
Last updated: 2022-01-04

blog Discussion dhowells blog (Discussion)
Forum for blog comments
Last updated: 2022-01-04

(no subject) dhowells wiki (Thread)
Last updated: 2022-01-04

Post by aliazzz on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
Last updated: 2022-01-04

Post by aliazzz on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
Hi, maybe it is an undocumented feature(?) but your request is allready implemented into v1.2.0.0 :-) AFAIK Use Test('Disabled_TestXYZ'); Test_Finished(); This will be counted in the reporting as a skipped test. (both logged in PLC Log and in the XML.report)
Last updated: 2022-01-04

wiki Discussion spetrean wiki (Discussion)
Forum for wiki comments
Last updated: 2022-01-04

blog Discussion spetrean blog (Discussion)
Forum for blog comments
Last updated: 2022-01-04

(no subject) spetrean wiki (Thread)
Last updated: 2022-01-04

Post by jtebokkel on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
Does TEST_FINISHED() need to be called when the test is marked as disabled_? or is it sufficient to just have it marked as skipped/disabled? METHOD T101_Process VAR_INPUT END_VAR VAR_INST mxT : UINT; END_VAR IF xLiveDB THEN TEST('T101_Process'); ELSE // gc_sDisable : STRING(10) := 'disabled_'; TEST(concat(gConst.gc_sDisable, 'T101_Process')); // Is this call necessary? TEST_FINISHED(); RETURN; END_IF CASE mxT OF 0: // init mxT := 10; 10: // multi stage test mxT := 20; ELSE TEST_FINISHED(); END_CASE
Last updated: 2022-01-04

Home spetrean wiki (WikiPage)
This is the personal project of spetrean. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-04

Post by jtebokkel on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
Did some digging on the format and I can't seem to find disabled as an attribute in the xsd (https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd) however skipped is mentioned, but in the context of <testsuite>
Last updated: 2022-01-05

Post by jtebokkel on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
It seems it is not reported as disabled in the xml report or in the log. (See attached screen shots), but is reported as SKIPPED in the test suite. Maybe I misunderstand the disabled field for <testsuites> I was expecting that to give the total disabled or skipped tests. It does get marked as skipped, but calling TEST_FINISHED() doesn't mark it finished. (Not sure if it should)
Last updated: 2022-01-05

Post by aliazzz on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
If you declare a test, calling TEST_FINISHED() is mandatory, even if the test will be disabled; TEST('DISABLED_ThisTestWillBeIgnored'); AssertEquals(Expected := a, Actual := b, Message := 'A does not equal B'); TEST_FINISHED(); Note that 'Disabled' is case insensitive.
Last updated: 2022-01-04

Post by aliazzz on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
status: open --> closed
Last updated: 2022-01-05

Ticket #56: Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Ticket)
It would be nice to add the ability to disable tests and have them listed in the xml report and logger report. I've got a situation where I have a some function blocks that I want to test. Most of the functionality can be tested in quick tests that only take a cycle or two, but some tests are dealing with timeouts that can make the test suite run for a few minutes. I'd like to be able to setup two configurations (through applications) that will disable the longer running tests so that I can quickly iterate my code. I have an input to my test suite function block that I can set to disable the longer running tests, but I have no easy way to know how many disabled tests there are when I run the quick config. If we could disable tests with a reason that would be even better. Then I could write a test for a future feature and have it shown as disabled rather than just failing before the feature is written. Thanks so much for the work that has gone into this project. It is really helpful and I greatly appreciate it.2022-01-05 06:51:26.609000 Ticket #56: Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS counit tickets tickets False /lib/counit/tickets/56/ Ticket Add ability to disable tests and have them reported False 3 2022-01-04 17:30:54.165000 56 Add ability to disable tests and have them reported closed It would be nice to add the ability to disable tests and have them listed in the xml report and logger report. I've got a situation where I have a some function blocks that I want to test. Most of the functionality can be tested in quick tests that only take a cycle or two, but some tests are dealing with timeouts that can make the test suite run for a few minutes. I'd like to be able to setup two configurations (through applications) that will disable the longer running tests so that I can quickly iterate my code. I have an input to my test suite function block that I can set to disable the longer running tests, but I have no easy way to know how many disabled tests there are when I run the quick config. If we could disable tests with a reason that would be even better. Then I could write a test for a future feature and have it shown as disabled rather than just failing before the feature is written. Thanks so much for the work that has gone into this project. It is really helpful and I greatly appreciate it. False False 0 0 0 None [FUTURE FEATURE] jtebokkel None
Last updated: 2022-01-05

Post by aliazzz on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
Since this ticket is fulfilled within scope I will close the issue.
Last updated: 2022-01-05

Post by aliazzz on #56 Add ability to disable tests and have them reported co♻e: A unittest framework for CODESYS tickets (Post)
XSD https://forge.codesys.com/prj/cfunit/code/HEAD/tree/trunk/coUnit/XSD/JUnitv5.xsd Compliance https://forge.codesys.com/prj/cfunit/code/HEAD/tree/trunk/coUnit/XSD/QA%20xUnit.xml%20template.png?format=raw
Last updated: 2022-01-05

wiki Discussion dcjarle wiki (Discussion)
Forum for wiki comments
Last updated: 2022-01-05

blog Discussion dcjarle blog (Discussion)
Forum for blog comments
Last updated: 2022-01-05

(no subject) co♻e: A unittest framework for CODESYS tickets (Thread)
Last updated: 2022-01-05

(no subject) dcjarle wiki (Thread)
Last updated: 2022-01-05

Home dcjarle wiki (WikiPage)
This is the personal project of dcjarle. This project is created automatically during user registration as an easy place to store personal data that doesn't need its own project such as cloned repositories.
Last updated: 2022-01-05

wiki Discussion mielcarek wiki (Discussion)
Forum for wiki comments
Last updated: 2022-01-05

blog Discussion mielcarek blog (Discussion)
Forum for blog comments
Last updated: 2022-01-05

<< < 1 .. 1494 1495 1496 1497 1498 .. 3647 > >> (Page 1496 of 3647)

Showing results of 91172

Sort by relevance or date