I am sure it does not come from that : I had this problem a while ago. Since then, I define all my new test objects by hand, choosing my own properties to identify the object. By the way, defining myself my own test objects make the smart identification disabled (it is on "False", but even if I wanted to change it, I couldn't).
But I just found something interesting : when identifying a unique object, when we want to add new properties, those ones are already filled with the correct value. So I checked it and it is filled with the properties of an other element later in the arborescence I am going through. However, it doesn't have the same "html id" at all ! So, I tried to take this element "html id" and the same thing happens : its other properties have an other element properties (well, after 2 times, it goes on an element I have already been through...).
Really weird...
But I just found something interesting : when identifying a unique object, when we want to add new properties, those ones are already filled with the correct value. So I checked it and it is filled with the properties of an other element later in the arborescence I am going through. However, it doesn't have the same "html id" at all ! So, I tried to take this element "html id" and the same thing happens : its other properties have an other element properties (well, after 2 times, it goes on an element I have already been through...).
Really weird...