What happened to the Unity Test Runner options? - unit-testing

Take a look at this screenshot (from this site):
Now look at a screenshot from my own copy of Unity (Personal).
As you can see, a lot appears to be missing. Does anybody know why? Is this a Pro-only thing? I can't find any reference to it.

The screenshot above is an older version of Test Tools. UnityTestTools was an open soruce project, deployed as a Package in the Asset Store. You had to import the asset from Asset Store to use this feature up to Unity 5.5. This is a deprecated project and is not supported anymore from Unity 5.6 (valid until Unity 5.5).
The Unity Technologies apparently liked it so they included the Test Tool as an official feature from Unity 5.6, and renamed it Test Runner. When you create projects you have the Test Runner included by default, which can be accessed from the tab [Window - Test Runner].
A few major changes I've noticed are:
AssertComponent no longer exists
No Scene-Based-Test out of the box as it used to be. Although Unity Forum suggests it should be easy to implement such tests yourself with PlayMode I feel like there are not enough ducumentation and examples for beginners.

Related

Microsoft ML can't use opset 11 despite nuget package installed

I'm trying to build a simple object detection runner, really just following this MS Docs guide: https://learn.microsoft.com/en-us/windows/ai/windows-ml/tutorials/tensorflow-deploy-model
I already figured out building the View and adding capabilities so the provided code actually compiles.
Just one more problem right now: When creating the session, it crashes claiming "Unknown model file format version" which seems to translate to "Opset of the model you use is not supported".
Looking at github issues google showed me, I'm supposed to install the Microsoft.AI.MachineLearning nuget package and all is well. Except when I installed it, nothing changed.
So, what's left to do beside open yet another github issue? I already re-exported my model from opset 15 to opset 11 because the nuget package only supports that.
I'm on windows 10, UWP targeting 2004.

Targeting a .NET Core 2.0.1 web project from a C# Test project based on .NET 4.7.1

I'm starting out with Test-Driven Development with Visual Studio 2017 Enterprise, but can't - however hard I've tried - make it work. I've tried trawling everywhere on the WWW to search for a solution, to no avail. So I hope that someone here will be able to help. The issue goes as follows:
I have created an ASP.NET Core web application, and a separate Test project; I'm using NUnit as the test framework (I first used xUnit but for some reason the tests disappeared and would not run). Anyway, when I try to reference my ASP.NET Core Web app from the test project, the following error shows up:
Project '..\MyProject\MyProject.csproj' targets 'netcoreapp2.1'. It cannot be referenced by a project that targets '.NETFramework,Version=v4.7'. UnitTestProject1
Does anyone have a clue about what can be wrong and how it can be fixed? Any help will be greatly appreciated.
Best regards.
EDIT
I am elaborating a little on the issue here. I try to illustrate it below. I have attached 3 images to show what I mean.
First, when I want to create a test project in Visual Studio, I go to the "Test" templates - and there I only see the templates shown in fig. 1 - there I have the possibility for selecting between different .NET versions as shown in the dropdown. Regardless of which one I selected I received the error mentioned in my earlier post.
Then, I tried using the .NET Core templates where I found 2 types of test projects: MSTest and xUnit tests (see fig. 2). MSTest is not usable in my case as it's a bit too limited for this exact application. Therefore, I tried using the xUnit test project. However, when I do that, the system complains about all sorts of libraries missing, and when looking in the "Dependencies" section in the solution explorer, all libraries are shown with a yellow "Warning" triangle on them (see fig. 3), and nothing compiles at all.
So I'm a bit stuck. Any ideas?
The test project is targeting .NET Framework 4.7 and the web project targets .NET Core App 2.1.
You cannot add a reference from one to another as they are incompatible.
To solve this you should create a test project that targets netcoreapp2.1 and add a reference from it to the web project.

.NET Core React Project Doesn't See NPM modules

I'm trying a React/Redux .NET core (2.0) web project in Visual Studio 2017. And I've installed font-awesome using npm. It's there and I can see it in the node_modules folder, but I'm not sure if the web project should see it automatically or if I have to drag it into my dist folder and edit my layout page to see it. I'm not against doing that, but as a VS programmer, I'm used to things being a bit more automatic mainly for the sake of package updates. I'm not really confortable editting the vendor.js or vendor-manifest.json files.
Anyone know what I'm doing wrong? (no guesses, please.)
I was looking for an answer to a similar question and came across FA's package specifically for React. They have some good instructions on this page.

Sonar runner is not listing the CxxCppCheckSensor while runner is started

I am new to sonar, i have installed sonarqube on RHEL 7 machine and its version is 5.1.1.
and the runner's version is 2.4.
I have four cpp related plugins, i tried with each one,
sonar-cxx-plugin-0.9.4-RC3.jar sslr-cxx-toolkit-0.9.4-RC3.jar
sonar-cpp-plugin-3.6.jar sonar-cpp-plugin-3.5.jar
sonar-cxx-plugin-0.9.jar
nothing seems to be listing the Sensor CxxCppCheckSensor . i need this for integrating cppcheck with the sonar. my cppcheck version is 1.68.
i have included sonar.cfamily.cppcheck.reportPath = in my sonar.project.properties file too.
Am I doing something wrong here ? Please help me out.
1.And do these cpp plugins needs license or trial key for proceeding?
2. Can cppcheck's xml report alone be viewed in sonar's dashboard?
Thanks in advance :)
sonar-cpp-plugin correspond to the commercial plugin and of course needs a license, sonar.cfamily.cppcheck.reportPath property is only for the commercial plugin.
sonar-cxx-plugin correspond to the community C++ plugin and has different properties.
Do not mix the two different plugins and documentation, pick one and follow one documentation installing only one of them.

Developing for BlackBerry with IntelliJ

I wonder if someone has idea about next.
I'm developing for BlackBerry. IDEA doesn't recognize RIM installation as JSDK or Mobile SDK. So I have create project without SDK and attach RIM jar file as dependency.
I'm trying to write as much as possible unit test with JUnit and Mockito but to run them IDEA requires JSDK. So I created additional module where I set JSDK, correct language level and it works. It's already hassle to create additional module (better if we could set JSDK and other compiler, runtime options for code and tests) but I was quite happy.
I have also dependencies for some common libraries which we use in android and J2ME also. I added them as modules with JSDK 1.6 and language level 1.3. And I able to develop and run test on it also.
But I got issue with LEDA EAP. IDEA now complaints about incompatibility with java.lang because it found them both in RIM jar and JSDK for libraries. And now I'm thinking about next hassle to fix my favorite ide. Sure it's EAP and things could be changed.
But anyone has any recommendation or similar situation setup?