Hello,
it seems I accidentally created an invalid unit test. Shortly after I realized that and fixed it.
ArgumentException: An item with the same key has already been added. Key: DeviceObject-UnitTests.dll/SitePlanner/ComponentParts_uTest/GetPartIDString_ShouldReturnCorrect_WhenDeviceIsCustom/[DeviceObject-UnitTests][SitePlanner.ComponentParts_uTest.GetPartIDString_ShouldReturnCorrect_WhenDeviceIsCustom(“Name”,“Name”)]2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) (at <252f5a151e57406087568ebdeb88d5fe>:0) System.Collections.Generic.Dictionary2[TKey,TValue].Add (TKey key, TValue value) (at <252f5a151e57406087568ebdeb88d5fe>:0)1[T] source, System.Func2[T,TResult] keySelector, System.Collections.Generic.IEqualityComparer1[T] comparer) (at <5daa034a65ef4e92beb94b6ef26af36a>:0) System.Linq.Enumerable.ToDictionary[TSource,TKey] (System.Collections.Generic.IEnumerable1[T] source, System.Func2[T,TResult] keySelector, System.Collections.Generic.IEqualityComparer1[T] comparer) (at <5daa034a65ef4e92beb94b6ef26af36a>:0)1[T] source, System.Func2[T,TResult] keySelector) (at <5daa034a65ef4e92beb94b6ef26af36a>:0)
Things I tried:
Changing the code in the test class
Deleting code in the test class
Deleting the test class/file
Deleting the assembly
Deleting library caches
(Of course) restarting Unity and my PC
Removing Test Framework in PackageManager and reinstalling it
Reinstalling Unity
Somehow I’m at a loss of what to do. I guess there is something in a some global cache that I can’t find.
Does someone have an idea?
Were you able to find a fix for this? I’m running into the exact same issue.
Well, not really.
"com.unity.test-framework": "2.0.1-pre.18",
At least it works somehow with this.
I was able to reproduce this bug and did bug report . Please vote
I solved the same problem by up-or-downgrading the “com.unity.test-framework” version and reverting to the original version after ensuring the problem was resolved.
There is probably a mechanism caching test case information outside of the project. So, running “git clean -fdx” inside the project does not remedy the problem.