Add failing tests, and actually trigger tests

sample-project/Assets/Tests/EditMode/SampleEditModeTest.cs

@@ -19,6 +19,8 @@ namespace Tests
 
       // Then
       Assert.AreEqual(1, counter.Count);
+
+      Assert.True(false);
     }
 
     [Test]
@@ -26,13 +28,13 @@ namespace Tests
     {
       // Given
       var counter = new BasicCounter(BasicCounter.MaxCount);
-      
+
       // When
       counter.Increment();
-      
+
       // Then
       Assert.AreEqual(BasicCounter.MaxCount, counter.Count);
     }
-    
+
   }
 }

sample-project/Assets/Tests/EditMode/SampleEditModeTest.cs.meta

@@ -6,6 +6,6 @@ MonoImporter:
   defaultReferences: []
   executionOrder: 0
   icon: {instanceID: 0}
-  userData: 
-  assetBundleName: 
-  assetBundleVariant: 
+  userData:
+  assetBundleName:
+  assetBundleVariant:

sample-project/Assets/Tests/PlayMode/SamplePlayModeTest.cs

@@ -14,6 +14,8 @@ namespace Tests
     {
       // Use the Assert class to test conditions
       Assert.True(true);
+
+      Assert.True(false);
     }
 
     // A UnityTest behaves like a coroutine in Play Mode. In Edit Mode you can use

sample-project/Assets/Tests/PlayMode/SamplePlayModeTest.cs.meta

@@ -6,6 +6,6 @@ MonoImporter:
   defaultReferences: []
   executionOrder: 0
   icon: {instanceID: 0}
-  userData: 
-  assetBundleName: 
-  assetBundleVariant: 
+  userData:
+  assetBundleName:
+  assetBundleVariant:

sample-project/ProjectSettings/ProjectSettings.asset

@@ -323,7 +323,7 @@ PlayerSettings:
     tvOS: 1
   m_BuildTargetGroupLightmapEncodingQuality: []
   m_BuildTargetGroupLightmapSettings: []
-  playModeTestRunnerEnabled: 0
+  playModeTestRunnerEnabled: 1
   runPlayModeTestAsEditModeTest: 0
   actionOnDotNetUnhandledException: 1
   enableInternalProfiler: 0