[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility

Monday, 25 December 2017

This is a multi-part message in MIME format...

------------=_1514218057-30883-100
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

     [
https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jir...
]

eyal edri updated OVIRT-1769:
-----------------------------
    Resolution: Won't Do
        Status: Done  (was: To Do)

As mentioned, if we want to run such scenario, we need to create a new suite for that,
with the relevant tests.
Having said that, I'm not sure its worth the resources over testing other flows which
are not covered yet.

...
 run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward
compatibility
 -----------------------------------------------------------------------------------

                 Key: OVIRT-1769
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769
             Project: oVirt - virtualization made easy
          Issue Type: New Feature
          Components: OST
            Reporter: danken
            Assignee: infra
            Priority: High

 starting with basic-suite-4.2, we port test cases to sdk4. That's good, since
that's the future of the project.
 However, as long as we promise backward compatibility for sdk3, we need to make sure it
does not break. This can be done by running basic-suite-4.1 tests on code of ovirt-master.

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)

------------=_1514218057-30883-100
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1769?page=com.atlassian.jir...
]</pre>
<h3>eyal edri updated OVIRT-1769:</h3>
<pre>Resolution: Won't Do
    Status: Done  (was: To Do)</pre>
<p>As mentioned, if we want to run such scenario, we need to create a new suite for
that, with the relevant tests. Having said that, I'm not sure its worth the resources
over testing other flows which are not covered yet.</p>
<blockquote><h3>run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3
packward compatibility</h3>
<pre>     Key: OVIRT-1769
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1769
 Project: oVirt - virtualization made easy
         Issue Type: New Feature
         Components: OST
Reporter: danken
Assignee: infra
Priority: High</pre>
<p>starting with basic-suite-4.2, we port test cases to sdk4. That's good, since
that's the future of the project. However, as long as we promise backward
compatibility for sdk3, we need to make sure it does not break. This can be done by
running basic-suite-4.1 tests on code of ovirt-master.</p></blockquote>
<p>&mdash; This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)</p>

------------=_1514218057-30883-100--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

[JIRA] (OVIRT-1769) run basic-suite-4.1 with ovirt-engine-master to ensure SDKv3 packward compatibility