Skip to content
New issue

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

Support additional test drivers in the etf-result-checker #99

Open
cportele opened this issue Dec 1, 2020 · 1 comment
Open

Support additional test drivers in the etf-result-checker #99

cportele opened this issue Dec 1, 2020 · 1 comment
Labels
EIP-draft Announcement. Will not be discussed further as long as the necessary information is available.

Comments

@cportele
Copy link
Contributor

cportele commented Dec 1, 2020

ETF Improvement Proposal (EIP)

This EIP is about a (potential) extension to the etf-result-checker tool, see #92. As it is stated in that EIP:

The tool is currently limited to test suites using the BaseX test driver, because assertion names have to be unique for each test run. This is not the case for SoapUI-based test suites.

This EIP discusses, if and how the etf-result-checker could support test suites for additional test drivers.

Background and Motivation:

In general, it would be good to have a mechanism for automated testing for all test suites. However, this may be different for SoapUI-based test suites given the status of SoapUI.

Proposed change

To be identified.

Alternatives

To be identified.

Funding

To be identified.

Additional information

n/a

@cportele cportele added the EIP-draft Announcement. Will not be discussed further as long as the necessary information is available. label Dec 1, 2020
@cportele
Copy link
Contributor Author

Meeting 2020-12-17: Do not support soapUI in etf-result-checker, but EIP #77 should be implemented so that etf-result-checker is supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EIP-draft Announcement. Will not be discussed further as long as the necessary information is available.
Projects
None yet
Development

No branches or pull requests

1 participant