We have made some architectural changes in vREST in version 2.5.0. Which required us to migrate your data according to new architecture.
Changes in vREST v2.5.0
- We have implemented test suite wise ordering of test cases in v2.5.0 instead of global ordering as implemented till v2.4.5.
- Earlier test suites were treated similar to tags. Now test suites are treated different from tags.
- Now test suites can have their own ordering.
- Now a Test Case can only linked to a single test suite.
- A test suite is a required property of the test case.
- A vREST project will have always at least single test suite.
Let us visualise the migration changes as shown in the following tables:
Before v2.5.0
| Test Case | TC Order | Linked Test Suites | Linked tags |
|---|---|---|---|
| TC 1 | 1 | Test Suite 1 | tag_1 |
| TC2 | 2 | Test Suite 1, Test Suite 2 | tag_1 |
| TC3 | 3 | Test Suite 3 | tag_1, tag_2 |
| TC4 | 4 | Test Suite 2 | |
| TC5 | 5 | Test Suite 1 | |
| TC6 | 6 | Test Suite 3 | tag_1 |
After v2.5.0
| Test Case | TC Order | Linked Test Suites | Linked tags |
|---|---|---|---|
| TC 1 | 1 | Migrated Test Suite | tag_1, ts_1_Test_Suite_1 |
| TC2 | 2 | Test Suite 1, Test Suite 2 | tag_1, ts_1_Test_Suite_1, ts_2_Test_Suite_2 |
| TC3 | 3 | Test Suite 3 | tag_1, tag_2, ts_3_Test_Suite_3 |
| TC4 | 4 | Test Suite 2 | ts_2_Test_Suite_1 |
| TC5 | 5 | Test Suite 1 | |
| TC6 | 6 | Test Suite 3 | tag_1 |