FullyQualifiableName not generated for examples (Azure Devops Test Case Association)

[MacostaHitachi]

Reason: I'm running into issues associating example scenarios to ADO after switching to reqnroll because examples are being generated as DataRow entries. Then Visual Studio can't determine the correct FullyQualifiableName to run these tests in the pipeline

Back on specflow there used to be a different function generated by example and I would like to get this feature

I see in Reqnroll repo that we have Reqnroll.Generator/UnitTestProvider/MsTestGeneratorProvider.cs that might give me that behavior back.

I know we can create a plugin and add our own provider I was able to do it like this

[assembly: GeneratorPlugin(typeof(AddTestNamePlugin))]
namespace TestMSTestReq
{
    public class AddTestNamePlugin : IGeneratorPlugin
    {
        public void Initialize(
            GeneratorPluginEvents generatorPluginEvents,
            GeneratorPluginParameters generatorPluginParameters,
            UnitTestProviderConfiguration unitTestProviderConfiguration)
        {
            // Register the decorator
            generatorPluginEvents.RegisterDependencies += RegisterDependencies;
        }
        private void RegisterDependencies(object sender, RegisterDependenciesEventArgs eventArgs)
        {
            eventArgs.ObjectContainer.RegisterTypeAs<MSTestCustomTestGenerationProvider, IUnitTestGeneratorProvider>("mstest");
        }
    }
}

but the above would require me to make a new project, add CI/CD for this and is just way too much customization.

Is there something simpler out there I can do just to achieve a function per example how the old behavior was?
I've tried configuring this from MSTest itself but wasn't successful to get a proper fullyqualifiablename from DataRows

[clrudolphi]

I believe you want to disable the "RowTest" feature and instead have the generator create a test method for each example row, is that correct?
If so, please see this section of the documentation and set 'allowRowTests' to false in your reqnroll.json configuration file.