C
cwright
Guest
Dider, * You can put your tests into any Procedure file or Class file. However this is not the recommended practice. You should keep your tests separate from business logic. The best approach (and one that happens automatically when you add the ablunit facet) is to create a "tests" directory. In there you put your test cases. Test cases can be organized into logical units through the use of test suits. * A test procedure / method should really only have a 1 to 1 ratio of test & assertion. This is why you have @before and @after annotations. If an assertion fails, then ABLUnit will go on to the next test. If your code errors out, the it will stop. * One example, that I illustrate when I engaged on CI/D is to begin with a test case that verifies system integrity. Such as the values in a control table or perhaps specific files on disk. * The window that displays the results in PDSOE is different for ABLunit as opposed to OEUnit. They are both xUnit formatted, so the display depends on the viewer. I know that when you import xUnit tests into Jenkins, they do not look like either. Hope this helps Cameron
Continue reading...
Continue reading...