Validate test artefacts upon their definition to avoid errors at test execution · Issue #7 · srdc/gitb · GitHub
More Web Proxy on the site http://driver.im/
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
Validation of test suite and test case XML files is possible in an offline manner by using the respective XML Schemas. However, there is significant room for errors that can go uncaught at the time of the test suite’s upload and that can cause unexpected problems upon execution. The test suite upload should be improved to fully validate provided input, from XML structure to content (e.g. matching transaction IDs, correct asset references, valid expressions) so that errors are caught before test case execution. This is particularly important considering that test case execution will often not be done by the test cases’ authors.
The text was updated successfully, but these errors were encountered:
Validation of test suite and test case XML files is possible in an offline manner by using the respective XML Schemas. However, there is significant room for errors that can go uncaught at the time of the test suite’s upload and that can cause unexpected problems upon execution. The test suite upload should be improved to fully validate provided input, from XML structure to content (e.g. matching transaction IDs, correct asset references, valid expressions) so that errors are caught before test case execution. This is particularly important considering that test case execution will often not be done by the test cases’ authors.
The text was updated successfully, but these errors were encountered: