NEW: Add integration test that uses native runtime (#952).

Author: Rene Damm

.yamato/upm-ci.yml

@@ -49,7 +49,7 @@ platforms:
     - upm-ci package pack --package-path ./Packages/com.unity.inputsystem/
     - upm-ci package test --package-path ./Packages/com.unity.inputsystem/ -u {{ editor.version }}
     - {% if platform.installscript %} {{ platform.installscript }} {{ editor.version }} {% endif %} 
-    - upm-ci~/tools/utr/utr --testproject=. --editor-location=.Editor --artifacts_path=upm-ci~/test-results/isolation-com.unity.inputsystem.tests --suite=playmode --api-profile=NET_4_6 --stdout-filter=minimal {% if platform.runtime %} --platform {{ platform.runtime }} {% endif %} {% if platform.scripting-backend %} --scripting-backend {{ platform.scripting-backend }} {% endif %} 
+    - upm-ci~/tools/utr/utr --testproject $PWD --editor-location=.Editor --artifacts_path=upm-ci~/test-results/isolation-com.unity.inputsystem.tests --suite=playmode --api-profile=NET_4_6 --stdout-filter=minimal {% if platform.runtime %} --platform {{ platform.runtime }} {% endif %} {% if platform.scripting-backend %} --scripting-backend {{ platform.scripting-backend }} {% endif %} 
   triggers:
     branches:
       only:
@@ -80,4 +80,4 @@ publish:
   artifacts:
     artifacts:
       paths:
-        - "upm-ci~/packages/*.tgz"
+        - "upm-ci~/packages/*.tgz"

Packages/com.unity.inputsystem/Tests/IntegrationTests.meta

@@ -0,0 +1,39 @@
+using NUnit.Framework;
+using UnityEngine.InputSystem;
+using UnityEngine.InputSystem.LowLevel;
+
+// These tests are the only ones that we put *in* the package. The rest of our tests live in Assets/Tests and run separately
+// from our CI and not through upm-ci. This also means that IntegrationTests is the only thing we put on trunk through our
+// verified package.
+//
+// Rationale:
+// (1) Our APIVerificationTests have extra package requirements and thus need a custom package manifest.json. This will not
+//     work with upm-ci.
+// (2) The tests we have in Assets/Tests exercise the input system in isolation. Having these run on trunk in addition to our
+//     CI in the input system repo adds little value while adding extra execution time to trunk QV runs. This is unlike
+//     the integration tests here which add value to trunk by making sure the input system is intact all the way through
+//     to the native input module.
+// (3) If we added everything in Assets/Tests to the package, we would add more stuff to user projects that has no value to users.
+//
+// NOTE: The tests here are necessary to pass the requirement imposed by upm-ci that a package MUST have tests in it.
+
+public class IntegrationTests
+{
+    [Test]
+    public void CanSendAndReceiveEvents()
+    {
+        var keyboard = InputSystem.AddDevice<Keyboard>();
+
+        try
+        {
+            InputSystem.QueueStateEvent(keyboard, new KeyboardState(Key.A));
+            InputSystem.Update();
+
+            Assert.That(keyboard.aKey.isPressed, Is.True);
+        }
+        finally
+        {
+            InputSystem.RemoveDevice(keyboard);
+        }
+    }
+}

Packages/com.unity.inputsystem/Tests/IntegrationTests/IntegrationTests.cs

@@ -0,0 +1,18 @@
+{
+    "name": "Unity.InputSystem.IntegrationTests",
+    "references": [
+        "GUID:75469ad4d38634e559750d17036d5f7c",
+        "GUID:dc04f38471c3a459fb4d31124ee9127d"
+    ],
+    "optionalUnityReferences": [
+        "TestAssemblies"
+    ],
+    "includePlatforms": [],
+    "excludePlatforms": [],
+    "allowUnsafeCode": false,
+    "overrideReferences": false,
+    "precompiledReferences": [],
+    "autoReferenced": false,
+    "defineConstraints": [],
+    "versionDefines": []
+}