Negative test or simulating a failure not possible with current method for a number of languages

julianghionoiu / dpnt-coverage

Collect coverage from SRCS files

0 stars 0 forks source link

Negative test or simulating a failure not possible with current method for a number of languages #35

Closed neomatrix369 closed 2 weeks ago

neomatrix369 commented 5 years ago

From the conversation logs on #34 we can see the below language runners need a different approach to propagate errors and fail fast:

[x] nodejs
[x] ruby
[x] csharp
[x] fsharp
[x] vbnet

Due to their inherent nature of not failing and we are not able to easily remove || true from the coverage scripts - as they would then always fail.

neomatrix369 commented 5 years ago

Ruby issue potentially resolved: https://github.com/julianghionoiu/dpnt-coverage/pull/34#issuecomment-458659720, subject to PR acceptance and merger

neomatrix369 commented 5 years ago

Nodejs issue potentially resolved: https://github.com/julianghionoiu/dpnt-coverage/pull/34#issuecomment-458664017, subject to PR acceptance and merger

neomatrix369 commented 5 years ago

CSharp issue potentially resolved: https://github.com/julianghionoiu/dpnt-coverage/pull/34#issuecomment-458673943, subject to PR acceptance and merger

neomatrix369 commented 5 years ago

FSharp issue potentially resolved: https://github.com/julianghionoiu/dpnt-coverage/pull/34#issuecomment-458678977, subject to PR acceptance and merger

neomatrix369 commented 5 years ago

VBNet issue potentially resolved: https://github.com/julianghionoiu/dpnt-coverage/pull/34#issuecomment-458682454, subject to PR acceptance and merger

neomatrix369 commented 5 years ago

In Maven and gradle we can ask it to ignore failing tests and it does not generate a non-zero exit code on finishing the build, we need to find how we could do that for the above 5 languages.