We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently when filling EOFTests expected output in case successful validtion is
ok.
At the same time many client team have the parsing tool implemented that does the same validating job, but output is like
OK e3000100,e50002,5f5f5fe4
(It is "OK" followed by the list of each code section contents)
In case of validation failure output format is the same.
It would be nice to reconcile these two formats, and not make client teams support additional one, i.e. make retesteth
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently when filling EOFTests expected output in case successful validtion is
At the same time many client team have the parsing tool implemented that does the same validating job, but output is like
(It is "OK" followed by the list of each code section contents)
In case of validation failure output format is the same.
It would be nice to reconcile these two formats, and not make client teams support additional one, i.e. make retesteth
2a. or better alternative to ignoring - change EOFTests format to list these code section contents in expectations.
The text was updated successfully, but these errors were encountered: