TestFramework

Ran into a strange issue with Azure Dev ops. I am trying to build my project in Azure Dev ops.

.Net Project structure looks like this in VS:

Here's what my Test project .csproj looks like:

Background: We use VS2019 and .NET 4.7.2 our current solutions. We use TFS 2015 SP3 and have numerous (60+) builds running unit tests with MSTest V2, etc. These use MSTest.TestAdapter and TestFramework up to 2.1.2.

So, I'm working with a new MSTest V2 project in a typical solution. I noticed MSTest.TestAdapter and TestFramework nuget packages do not seem to work with TFS 2015 SP3. In the build log, I do see the following error: no test found. make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.

I cannot figure out what to do to get the 2.2.3 packages to work with TFS. If I downgrade those two packages to 2.1.2, the tests will run just fine in TFS. Is this just a case of TFS 2015 being too old?

I'd like to stay as current as I can, given the TFS constraint. Is there a way to get the TestAdapter and TestFramework 2.2.3 (or future releases) to work with TFS 2015 SP3?

Thanks in advance!

I have created a framework with few cocoapod dependencies .The archive for the framework is failing when i do 'xcodebuild archive' after adding the pod files (Did pod install).

In the normal build, it is working fine. There is no error and the build is successful but when I do 'xcodebuild archive' on my terminal got this below issue.

Currently we have a github repo where we store all the contracts, another repo which contains the producer code, and last but not least another one which contains the consumer code.

On the consumer side working with branches when pointing to the contract repo is well supported by using properties like stubrunner.properties.git.branch (more info can be found here https://cloud.spring.io/spring-cloud-contract/reference/html/appendix.html#additional-application-properties)

But on the producer I can not see any way of using the contracts of a concrete branch, we just can point to the github repo where contracts are stored by using contractsRepositoryUrl of the spring-cloud-contract-maven-plugin

This will be very useful to create a flow of contract testing :

• a PR to contract testing repo with the proposal
• which will trigger the producer job (passing the pr branch name)
• if the repo with the contracts contains the bindings, populated by the producer(previous step), then we could trigger the consumer job and validate if everything is fine with these proposed changes
• once the 2 builds are green (producer and consumer) we can merge the changes on the contracts repo

UPDATE : the following spring-cloud-contract-maven-plugin config worked for me, also you can set this property through command line like this -Dstubrunner.properties.git.branch=other_branch_than_master

I am using Moq and AutoFixture.

Given the following interfaces:

I try to set up a test project in Visual Studio 2019.

The module that I want to test is written in c.

I'm using the native VS cpp Testframework.

I can compile and run my program but not my unittest. Once I try to run that one I get the following error:

Fehler LNK2019 Verweis auf nicht aufgelöstes externes Symbol "_is_prime" in Funktion ""public: void __thiscall UnitTest1::UnitTest1::TestMethod1(void)" (?TestMethod1@UnitTest1@1@QAEXXZ)". UnitTest1 C:\Users\Alexander Leibenath\Documents\20210210_Prime_VS\Primzahlprüfer\Primzahlprüfer\UnitTest1\UnitTest1.obj 1

What I've tried so far:

• told the comiler in the header file that if he is a cpp compiler he should interpret the c-functions as c

Here is my code:

I'm trying to configure visual studio code to run my java project which is using Play framework.

After installing Scala(Metal), there was an error:

I have created a new project and am trying to set up the production environment properly. I haven't added any entities yet so it's still an empty JHipster project! Unfortunately Elasticsearch keeps throwing an exception and it doesn't work out of the box.

Exception: