Skip to content

Conversation

@bart-degreed
Copy link
Contributor

This ensures all projects in the solution are built in release mode and all unit tests in all projects in the solution are run.

Also removed outdated/broken additional solution files.

@bart-degreed
Copy link
Contributor Author

@maurei The failing AppVeyor builds puzzles me. Thoughts?

Bart Koelman added 2 commits February 13, 2020 18:33
The problem: NoEntityFrameworkTests project has a reference to UnitTests project, which has a reference to JsonApiDotNetCoreExampleTests project, which has a reference to JsonApiDotNetCoreExample project. The last one contains an appsettings.json file with connection string to JsonApiDotNetCoreExample database. So when building, this file may end up in the output directory of NoEntityFrameworkTests project, overwriting the appsettings.json (containing the connection string to JsonApiDotNetCoreNoEFCoreExample database) from NoEntityFrameworkExample project.

Next, if the NoEntityFrameworkTests testset runs first, it populates the JsonApiDotNetCoreExample database from models intended for the JsonApiDotNetCoreNoEFCoreExample database. And this causes subsequent test projects to fail.
@maurei
Copy link
Member

maurei commented Feb 13, 2020

Looks like you've figured it out. Let me know if this is the final state of the PR

@bart-degreed
Copy link
Contributor Author

I haven't been able to find the root cause of the failures (which worries me), but running the tests in a fixed order (workaround) seems to work. So this is ready for merge.

@maurei maurei merged commit 668f071 into json-api-dotnet:master Feb 13, 2020
@bart-degreed bart-degreed deleted the ci-auto-discovery branch February 13, 2020 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants