You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current solution of reporting asserts is not bullet-proof. Although the code says it checks for the complete combination of:
Test message
Test instance path
Expected value
Actual value
It actually only checks for the first instance of test message/test instance path AND THEN checks if the expected value and actual value are according to the result as well. What the reporting should do is to check if the combination of all four exist.
For arrays it needs to be done differently. Here we need to replace the expected & actual value with the size of both arrays and the types of both arrays.
Question: Is it possible to add a identifier to every assert? If we assume that every assert is called at every cycle, we can create an index for every assert in every test suite.
The text was updated successfully, but these errors were encountered:
Issue tcunit#15 - "The verifier wastes quite a bit of time"
Issue tcunit#17 - "There's no need to add any attributes to test suites"
PR tcunit#16 - "Feature/speed up"
Issue tcunit#18 - "Discrepancy between 4022 and 4024 in TIME_TO_STRING makes tests fail"
The current solution of reporting asserts is not bullet-proof. Although the code says it checks for the complete combination of:
It actually only checks for the first instance of test message/test instance path AND THEN checks if the expected value and actual value are according to the result as well. What the reporting should do is to check if the combination of all four exist.
For arrays it needs to be done differently. Here we need to replace the expected & actual value with the size of both arrays and the types of both arrays.
Question: Is it possible to add a identifier to every assert? If we assume that every assert is called at every cycle, we can create an index for every assert in every test suite.
The text was updated successfully, but these errors were encountered: