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
To keep the automation library completely standalone from the code of the framework, we should only rely on the ovs-extensions package (for logging, lightweight) and the api.
Currently a lot of helper calls are ugly wrappers around certain api tasks and all information is still being fetched from the DAL itself instead of the API
This will be the basis of QA 2.0
The text was updated successfully, but these errors were encountered:
@jake9050 could you investigate if all necessary api calls are available before starting with this way to go direction. Please use this ticket to list what is missing.
All calls to support the current tests are sufficient for the improvement I was keen on.
The reason for this ticket is to have a 'model' which completely relies upon the api and work from that instead of calling 1001 helper functions
Feature description
To keep the automation library completely standalone from the code of the framework, we should only rely on the ovs-extensions package (for logging, lightweight) and the api.
Currently a lot of helper calls are ugly wrappers around certain api tasks and all information is still being fetched from the DAL itself instead of the API
This will be the basis of QA 2.0
The text was updated successfully, but these errors were encountered: