Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Tests on traceability when moving projects

1. creation of a data model with one requirement type R, one scope S and one traceability link type « R2R » between requirements.

2. creation of a project with 5 requirements R1 to R5 (created with local requirement source)

3. export Recycle configuration and store it in the project.

4. creation of 4 links between those requirements through traceability creator: R1-R2, R1-R3, R1-R4, R1-R5 => can see them immediately in the table.

5. Deletion of first link => it works.

6. Share project to Git (or Perforce) and commit project (all files)

7. Deletion of second link => it works (removed from table)

8. Creation of 2 new links: R2-R3 and R2-R4 => can see them in the table

9. Deletion of last link (R2-R4) => it works

And we can continue with project import by reference:

10. Creation of another workspace WS2

11. Import previous project (import..> existing projects into workspace and select project from git location) - leave « copy in workspace » UNCHECKED to get a reference (not a copy)

12. import Recycle configuration. Can now see requirements and the 3 links in the traceability table.

13. Creation of 1 link R3-R4 (can see it)

14. deletion of R1-R4 => removed

15. Deletion of R3-R4 => removed

We get now 2 links in table: R1-R5 and R2-R3

Now same import of project but with copy.

16.Delete current project from WS2 but do not delete from disk (just from workspace).

17. Import project from git location but check « Copy in workspace »

18. create 2 links R3-R4 and R3-R5

19. deleteR1-R5

20 delete R3-R5 => works

[back to ReqCycle wiki main page: https://polarsys.org/wiki/ReqCycle]

Back to the top