Missing source information (CodeFilePath, LineNumber) in discovered test cases for .NET Core (3.x?) projects with "Full" PDB (instead of "Portable" PDB)

Description

Hi,

I’m using VsTestConsoleWrapper API to discover test cases.

When the test assembly is compiled to .NET Core (3.x?) and is configured to produce Full PDB instead of default Portable PDB, the discovered TestCase have null CodeFilePath and LineNumber is -1.

After switching to Portable PDB the CodeFilePath and LineNumber are correct.

As you can see in next comment, it looks like a regression, because it works correctly if unit test project targets .net core 2.1

Steps to reproduce

I’m attaching:

• ConsoleApp5.zip - project with unit tests
• VstestTest.zip - project which uses VsTestConsoleWrapper to discover and display test cases

Reproduction:

1. unpack ConsoleApp5, verify unit test projects use Full PDBs, compile
2. unpack VstestTest, compile
3. download microsoft.testplatform nuget, unpack
4. run VstestTest, for example:

D:\dv.scripts\vstest_repro\VstestTest\VstestTest\bin\Debug\VstestTest.exe ^
    D:\dv.scripts\vstest_repro\microsoft.testplatform.16.4.0\tools\net451\Common7\IDE\Extensions\TestPlatform\vstest.console.exe ^
    D:\dv.scripts\vstest_repro\ConsoleApp5\UnitTestProject1\bin\Debug\netcoreapp3.1\Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter.dll ^
    D:\dv.scripts\vstest_repro\ConsoleApp5\UnitTestProject1\bin\Debug\netcoreapp3.1\UnitTestProject1.dll

1. observe missing CodeFilePath and incorrect LineNumber in output
2. modify ConsoleApp5 to use Portable PDB, recompile it, rerun VstestTest, observe correct values

Expected behavior

DisplayName=TestMethod1
CodeFilePath=D:\dv.scripts\vstest_repro\ConsoleApp5\UnitTestProject1\UnitTest1.cs
LineNumber=11

Actual behavior

DisplayName=TestMethod1
CodeFilePath=
LineNumber=-1

Diagnostic logs

I’m attaching:

• logs.zip - vstest logs and output

Environment

I have used vstest from nuget packages microsoft.testplatform.16.4.0 and microsoft.testplatform.16.5.0-preview-20191115-01.

I’m testing this on Windows 10.

[tobyash86]

I can confirm this issue as well. Currently, it is a blocker for me. Can anybody help with that?

[pkrukp]

It works correctly when tested project targets .net core 2.1 (2.x?) - source information is present for both portable and full PDB. So this looks like a regression.

I may be wrong, but I think I read somewhere about DIA update in .net core 3.x - I may be wrong though.

Attaching

• ConsoleApp6.zip - project with unit tests, targetting .net core 2.1