Community
Participate
Working Groups
Build Identifier: 3.6.1 M20101201-0800 TPTP-4.7.2-201012121900 Test case "test name check on editor for existing resource" from Test.UI.TestNavigator.bugzilla_166025 is failling. It is possible to rename an artifact with the "resource name" of another existing artifact. Reproducible: Always Steps to Reproduce: 1. Create an empty project 2. In previous project, create two artifacts, one named "a" and one named "b" 3. open editor of artifact "a", rename it (via editor) into "c". save the artifact (via editor). 4. open editor on artifact "b", put an empty name and try to save. Check that an error message appear and that save is not performed (editor stay in "dirty" mode)
Victor, Is this a regression from TPTP 4.7.1? Tentatively targeting to 4.7.2. Jerome, please take a look.
ok, i can reproduce it but with theses steps : Steps to Reproduce: 1. Create an empty project 2. In previous project, create two artifacts, one named "a" and one named "b" 3. open editor of artifact "a", rename it (via editor) into "c". save the artifact (via editor). 4. open editor on artifact "b", put "a" as name and try to save. => an error should appear in theory (as it is, save is really performed) checking what is happening
after some examination, i remind that we changed a bit the naming rules but we forgot to update the manual test actual rules are : . logical name is not empty . logical name is be valid : - does not starts or ends with "-", " " or "." - does not contains ":", "\" or "/" . logical name does not already exists under the same container so, theses test should work : 1. Create an empty project 2. In previous project, create two artifacts, one named "a" and one named "b" 3. open editor of artifact "a", rename it (via editor) into "c". save the artifact (via editor). 4. open editor on artifact "b", put an empty name and try to save. Check that an error message appear and that save is not performed (editor stay in "dirty" mode) 5. open editor on artifact "b", put "c" as name and try to save. Check that an error message appear and that save is not performed (editor stay in "dirty" mode) will update manual test and will close bug when done
manual test 166025 updated closing
updating worked time
