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 workflow of ETF v2 has been mainly developed for public deployments: the
user selects an ETS, uploads the test data or enters the URL of a web service
and starts the test run. To rerun modified datasets or web services, you need
to upload files or reenter the URL of the service again.
Within an organization that mostly tests the same services with specific URL
or datasets that are in specific locations, this workflow should be optimized.
Proposed change
Create an alternative web interface for workflow in non-public deployments
that facilitates the re-running of tests with preconfigured Test Objects and
ETSs.
The workflow could be made configureable in the etf-config.propeties
configuration file. The default workflow would be set to "simple" for public
deployments. The new workflow could be named "org-internal".
Instead of choosing one or multiple Executable Test Suites, the user would
either:
select a Test Object and then select which ETSs should be executed
select a TestRunTemplate and run a set of Executable Test Suites against a
preselected Test Object
select a TestRunTemplate and then select a Test Object
Of course there must also be dialogues for creating and deleting
Test Objects and Test Run Templates.
This is a draft version. A concept for the web interface of the new workflow
will be submitted soon.
Alternatives
draft, not yet considered
Funding
Full funding available.
Additional information
Organizational workflows were already implemented once in ETF version 1
and were the default workflows there. Due to technical changes, these can
can not be reused.
This EIP should be compatible with existing ETSs
This EIP should not affect existing deployments
The text was updated successfully, but these errors were encountered:
ETF Improvement Proposal (EIP)
This is a draft
Background and Motivation:
The workflow of ETF v2 has been mainly developed for public deployments: the
user selects an ETS, uploads the test data or enters the URL of a web service
and starts the test run. To rerun modified datasets or web services, you need
to upload files or reenter the URL of the service again.
Within an organization that mostly tests the same services with specific URL
or datasets that are in specific locations, this workflow should be optimized.
Proposed change
Create an alternative web interface for workflow in non-public deployments
that facilitates the re-running of tests with preconfigured Test Objects and
ETSs.
The workflow could be made configureable in the etf-config.propeties
configuration file. The default workflow would be set to "simple" for public
deployments. The new workflow could be named "org-internal".
This EIP is based on the EIP #26 and EIP #28.
Instead of choosing one or multiple Executable Test Suites, the user would
either:
preselected Test Object
Of course there must also be dialogues for creating and deleting
Test Objects and Test Run Templates.
This is a draft version. A concept for the web interface of the new workflow
will be submitted soon.
Alternatives
draft, not yet considered
Funding
Full funding available.
Additional information
and were the default workflows there. Due to technical changes, these can
can not be reused.
The text was updated successfully, but these errors were encountered: