Fail localization test with inconclusive.

To avoid breaking the build, which happens for almost all pull requests of new units that do not have the Russian translations.
Using inconclusive flags the test so it is easy to spot, but does not prevent the test from succeeding overall.
Consider moving back to failing when a better solution for translations and/or pull request reviews is found.

Author: angularsen

Tests/UnitSystemTests.cs

@@ -49,9 +49,18 @@ public void AllUnitAbbreviationsImplemented([Values("", "en-US", "nb-NO", "ru-RU
                     unitsMissingAbbreviations.Add(unit);
                 }
             }
-            
-            Assert.IsEmpty(unitsMissingAbbreviations,
-                "Units missing abbreviations: " + string.Join(", ", unitsMissingAbbreviations.Select(u => u.ToString()).ToArray()));
+
+            // We want to flag if any localizations are missing, but not break the build
+            // or flag an error for pull requests. For now they are not considered 
+            // critical and it is cumbersome to have a third person review the pull request
+            // and add in any translations before merging it in.
+            if (unitsMissingAbbreviations.Any())
+            {
+                string message = "Units missing abbreviations: " +
+                                 string.Join(", ", unitsMissingAbbreviations.Select(u => u.ToString()).ToArray());
+                Assert.Inconclusive("Failed, but skipping error for localization: " + message);
+            }
+            //Assert.IsEmpty(unitsMissingAbbreviations, message);
         }
 
         [Test]