Displaying 4 results from an estimated 4 matches for "forceallerrors".
2017 Jul 31
2
Test Error Paths for Expected & ErrorOr
...>> of errors passed between function call hierarchies in more complex
>>> scenarios.
>>> For this I should point to the other example in the code, where it's
>>> applied to llvm::object::createBinary():
>>>
>>> https://github.com/weliveindetail/ForceAllErrors-in-LLVM/blob/master/test/TestLLVMObject.h#L13
>>>
>>> Here it detects and runs 44 different control paths, that can hardly be
>>> covered by a unit test altogether, because they don't depend on the input
>>> to creatBinary() but rather on the environment the...
2017 Jul 28
3
Test Error Paths for Expected & ErrorOr
...also verify correct handling
>> of errors passed between function call hierarchies in more complex
>> scenarios.
>> For this I should point to the other example in the code, where it's
>> applied to llvm::object::createBinary():
>> https://github.com/weliveindetail/ForceAllErrors-
>> in-LLVM/blob/master/test/TestLLVMObject.h#L13
>>
>> Here it detects and runs 44 different control paths, that can hardly be
>> covered by a unit test altogether, because they don't depend on the input
>> to creatBinary() but rather on the environment the test r...
2017 Jul 27
2
Test Error Paths for Expected & ErrorOr
...In contrast to unit tests, however, it can also verify correct handling
of errors passed between function call hierarchies in more complex
scenarios.
For this I should point to the other example in the code, where it's
applied to llvm::object::createBinary():
https://github.com/weliveindetail/ForceAllErrors-in-LLVM/blob/master/test/TestLLVMObject.h#L13
Here it detects and runs 44 different control paths, that can hardly be
covered by a unit test altogether, because they don't depend on the
input to creatBinary() but rather on the environment the test runs in.
Am 27.07.17 um 16:46 schrieb David B...
2017 Jul 27
2
Test Error Paths for Expected & ErrorOr
...nd issues in the execution paths of my
error cases and got annoyed by their naturally low test coverage.
So I started sketching a test that runs all error paths for a given
piece of code to detect these issues. I just pushed it to GitHub and
added a little readme:
https://github.com/weliveindetail/ForceAllErrors-in-LLVM
Are there people on the list facing the same issue?
How do you test your error paths?
Could this be of use for you if it was in a reusable state?
Is there something similar already around?
Anyone seeing bugs or improvements?
Could it maybe even increase coverage in the LLVM test suite some...