[Question] How to pass AnalyzerConfigOptions when unit testing

[j0shuams]

When working on a component of a SourceGenerator, I was writing unit tests to check for diagnostics getting raised on the compilation context created by a source code string. We have a downstream check that checks a compilation's AnalyzerConfigOptions for a specified assembly name. When you create a compilation context in a unit test, there's no project file to specify a property AssemblyName, so this check returns null and causes issues.

Here is where I do this and would like to pass some kind of optionsProvider containing a mapping for "AssemblyName" to something like "TestNamespace", and any other properties we might need.

Please advise on how I would be able to do this. Let me know if you need more information.

I'm using these packages:

Microsoft.CodeAnalysis.CSharp.Workspaces, Version="3.8.0-4.20472.6"
Microsoft.CodeAnalysis.Analyzers, Version="3.3.0"

[jmarolf]

I would recommend using Microsoft.CodeAnalysis.Testing from here. There should be properties on the ProjectState or SolutionState to add your own custom AnalyzerConfigOptions @sharwell is that correct?

[Youssef1313]

@jmarolf Does the testing library work for source generators? I thought it didn't.

[sharwell]

There should be properties on the ProjectState or SolutionState to add your own custom AnalyzerConfigOptions @sharwell is that correct?

It wasn't correct, but I just added support in #734.

Does the testing library work for source generators?

@Youssef1313 Yes, you can use Microsoft.CodeAnalysis.CSharp.SourceGenerators.Testing.XUnit (or equivalent for other language/frameworks).

[Youssef1313]

@Youssef1313 Yes, you can use Microsoft.CodeAnalysis.CSharp.SourceGenerators.Testing.XUnit (or equivalent for other language/frameworks).

This is great! May you update the README for usage examples?

[sharwell]

Filed #737 to add the packages to the list, but haven't added examples yet