Francois Normandin

As a side note, there are no ways to mark a test as skipped in Caraya without wiring an error in the assertion method. That's because assertions are not tests....

@AndreasStark it seems you would like a behavior such as the one in pyTest which defines "skip" and "expected to fail" as modifiers that can be added. https://docs.pytest.org/en/latest/skipping.html Let me...

Hi @felipefoz , I have responded to a similar question a while back on the JKI Forums. https://forums.vipm.io/topic/3686-code-coverage/ I don't pretend that this was a good answer, as there might...

Hi @felipefoz , Sorry to revive this old thread, but I wanted to document that the new Test and Assert properties in Caraya 1.4.0+ could be used to build a...

Note for future: - This "branch" was added to get a registry of the skipped tests, such as those that are out-of-scope. Keep that in consideration while addressing this issue.

I'm the culprit. I had decided to extend the release notes until we updated the Minor build number. My reasoning was that while we are in 0.6.x.x, we are really...

@joerghampel The issue #95 was closed, so I'm referencing your ask in this new thread.

It is conceivable, yes. The piping for public events when run as part of a Suite is there, so it's a matter of defining what makes sense for information to...

I propose the following schemas, events to be published as JSON payloads. Test Registration Event: ``` { "test-uid": "myTestID", "test-name" : "myTestName", "timestamp": "ISO timestamp", "caller-uid": "myCallerTestID", "call-chain": ["", "",...

The events are not ordered. Caraya will execute them in different order depending on how you wire the error terminals and how many tests are launched in parallel. You will...