Closed plocket closed 5 months ago
I am unable to replicate this "duplicate row" warning message in our tests, even though I have seen it in multiple other repositories.
I now believe the duplicate row issue is a red herring. Current hypothesis: The way a text field is interacted with does nothing to clear the text that is already in the field. This is fine in a lot of cases, but when the field has a default value, it's a problem. The test was fine the first time because the value was from a DAGlobal and that value had not been set before. The next times the test was run, the DAGlobal did have a value and the field already had an answer, so the Story Table just added more text to that answer.
My guess is that duplicate rows are being created for some fields and, instead of ignoring them, ALKiln is entering the values twice.
I think this has something to do with the new code that uses proxy vars. It somehow generates duplicate fields. It seems that happens with more than just fields with value choices.
Alternatively, it might have to do with how text is being typed now.