Duplicate IDs - Klaros Test Management - Forum - Klaros-Testmanagement
Duplicate IDs
Mark K. Plueckhahn, geändert vor 12 Jahren.
Duplicate IDs
Youngling Beitrag: 1 Beitrittsdatum: 13.07.11 Neueste Beiträge
While working with a colleague in the same project, each of us is creating new test cases.
If both of us hit the button "Neu" to create a new testcase work on these testcases and save them in the end,
both testcases get the same (unchangeable) ID.
Please see attachment.
Now if browsing through the testcases with "Voriger Testfall" / "Nächster Testfall" only one of these entries with duplicate IDs is reachable.
Using Community Edition 3.4.2 - Build 1101 (2011-05-27 16:55:27) on a Postgres Database.
If both of us hit the button "Neu" to create a new testcase work on these testcases and save them in the end,
both testcases get the same (unchangeable) ID.
Please see attachment.
Now if browsing through the testcases with "Voriger Testfall" / "Nächster Testfall" only one of these entries with duplicate IDs is reachable.
Using Community Edition 3.4.2 - Build 1101 (2011-05-27 16:55:27) on a Postgres Database.
Torsten Stolpmann, geändert vor 12 Jahren.
RE: Duplicate IDs
Jedi Council Member Beiträge: 755 Beitrittsdatum: 12.02.09 Neueste Beiträge
Hi Mark,
our current analysis shows that there is indeed a race condition leading to this bug, thanks a lot for pointing this out.
I tracked this as KLAROS-1345 (Duplicate IDs are generated when saving new test cases simultaneously in different sessions). This behavior will show when two save requests for newly created objects are overlapping.
The fact that one of the test cases is not shown when browsing through the test cases is due to the application regarding the second one a revision of the former test case. Your database is still consistent (IDs are not used as database keys), but I would advise duplicating and deleting one of the conflicting test cases until this issue has been resolved.
Thanks again for your feedback,
Torsten
our current analysis shows that there is indeed a race condition leading to this bug, thanks a lot for pointing this out.
I tracked this as KLAROS-1345 (Duplicate IDs are generated when saving new test cases simultaneously in different sessions). This behavior will show when two save requests for newly created objects are overlapping.
The fact that one of the test cases is not shown when browsing through the test cases is due to the application regarding the second one a revision of the former test case. Your database is still consistent (IDs are not used as database keys), but I would advise duplicating and deleting one of the conflicting test cases until this issue has been resolved.
Thanks again for your feedback,
Torsten