Regression of unfound test assembly - 2019.3.0f3 - package 1.0.0-preview.3

[builder-main]

I'm having an issue with the test assembly although I followed the guide in https://docs.unity3d.com/Packages/com.unity.inputsystem@1.0/manual/Testing.html, package does not show up in assembly explorer and references can't resolve. 2019.3.0f3 - package 1.0.0-preview.3

As a side note, the assembly is not present in Library\ScriptAssemblies.

using UnityEngine.InputSystem;

    [TestFixture]
    public class BindingInputTest : InputTestFixture

My test assembly configuration :

Originally posted by @MorphiksBuilder in #366 (comment)

[MeikelLP]

Still broken in preview 4. This is bonkers even for a preview. Quality assurance is a big topic it seems.

[Rene-Damm]

Unfortunately, due to how this works now in the package manager, it now requires a workaround that isn't mentioned in the docs page.

Basically, in your Packages/manifest.json file, you need to add

"testables" : [ "com.unity.inputsystem" ]

in order for the test framework assembly to be included in test builds.

I'll see if we can find a better solution or at least make sure this bit gets included in the docs.

[Rene-Damm]

Also just noticed that doing this now results in an integration test test from the input system showing up in user projects, too. It's the only test that gets added directly to the package ATM. Looking into it.

[MeikelLP]

@Rene-Damm your workaround testables does not work for me.

[Rene-Damm]

@MeikelLP Could you provide some more details? What's the error? What exactly isn't working?

I've tried the setup with 1.0.0-preview.4 and after adding the snippet to Packages/manifest.json was able to set up a test assembly just fine. Other than having to modify the manifest in the first place, only wart was the input system injecting a test into the project.

[MeikelLP]

I get the exact same error as the OP

[Rene-Damm]

Is the file in a separate test assembly that references the input system test framework assembly?

[MeikelLP]

it is yes. I'm working with several assembly definition files

[Rene-Damm]

Please file a ticket with the Unity bug reporter. We'll have a look.

[MeikelLP]

So today on my personal machine I installed Unity 2019.3.1f1 and it seems to be fixed when setting the testables like @Rene-Damm said.

[jo3w4rd]

Would this page have helped you with your problem if you had found it?
https://docs.unity3d.com/Manual/cus-tests.html

[MeikelLP]

@jo3w4rd I don't want to include the tests of a package. I want to use a class inside a package which wasn't possible without testables

[stefanunity]

Hello,

we're going to close all the github issues and will concentrate bug information in the Unity public issue tracker https://issuetracker.unity3d.com/product/unity/issues?project=116&status=1&unity_version=&view=hottest.

If you are still experienceing this issue in the latest package version please do file a bug report as described here https://unity3d.com/unity/qa/bug-reporting
For general feedback and discussions you can go to https://forum.unity.com/forums/new-input-system.103/

Thank you!

[builder-main]

This issue is still alive for us, unity 2019.3.11f1 and the latest package 1.0.0. We're not creating a package, simply having an asmdef for our playmode tests.

We've added in the manifest : "testables" : [ "com.unity.inputsystem" ]

[EDIT] : We added the compile flag UNITY_INCLUDE_TESTS and it seems to work