Test-framework: Experimental/unmoving since 2022?!

[MrLucid72]

com.unity.test-framework has been stuck in 1.x since 2022 when 2.x has been “experimental” since… well, also 2022!

Was this package abandoned? Why is it still experimental? I want it for the async/await [Test] support.

[Spy-Master]

@MrLucid72

com.unity.test-framework has been stuck in 1.x since 2022 when 2.x has been “experimental” since… well, also 2022!

Was this package abandoned? Why is it still experimental? I want it for the async/await [Test] support.

2.0 was problematic, they’ve backported some features onto 1.x and not continued on 2.0 directly.

Unity Test Framework 2.0 ready for feedback

The decision to not continue work on 2.0 was done because of the issues validating and releasing it internally. We simply had too many test projects that was working on 1.x, but failing on 2.0 unintendedly. Due to that, we choose the approach of uptaking the 2.0 changes one by one. This ensures that we can validate each individual change against all of our internal test projects. The drawback is that is taking longer time, but the upside, is that the end results is of a higher quality. Our int…

Async tests are available since 1.3.x, you don’t need 2.0 for this.

[MrLucid72]

Ah, I read lacking support - probably misread. Thanks! Will downgrade.

However, even then – how come no active development? It’s been years! It feels like it was an excuse for just halting development completely, portraying “Well, we’re out of budget; let’s just revert back to v1.x and not touch it for a few years+++; maybe no one will notice”.

It has a lingering feeling of deprecation in the back of my head similar to that of UNET or the old Text engine.