CSharp Generator Related: Unit Test(s) generated are commented out

Description

After generating a Client library for a given api, the Unit Test Project that is generated contains test assertions which are commented out and comments in the generated code reading // TODO uncomment below to test the method and replace null with proper value

Generated code example portion relevant:

       /// <summary>
        /// Test ApiSomePostMethod
        /// </summary>
        [Test]
        public void ApiSomePostMethodTest()
        {
            // TODO uncomment below to test the method and replace null with proper value
            //SomePostMethodRequest SomePostMethodRequest = null;  // **THIS TYPE IS AVAILABLE VIA SCHEMA**
            //var response = instance.SomePostMethod(SomePostMethodRequest); // **THIS TYPE IS AVAILABLE VIA SCHEMA**
            //Assert.IsInstanceOf(typeof(SomePostMethodResponse), response, "response is SomePostMethodResponse");// **THIS TYPE IS AVAILABLE VIA SCHEMA**
        }

openapi-generator version

@openapitools/openapi-generator-cli@2.4.4

OpenAPI declaration file content or url

n/a - any csharp generator resulting Test Project will suffice

Command line used for generation

due to the CI environment, the call line is a little hairy, thanks for understanding

"node node_modules\\@openapitools\\openapi-generator-cli\\main.js generate -i swagger.json -g csharp -o $workspace\\gen --additional-properties=packageName=$SDKProjectName"

Steps to reproduce

just generate a csharp project set

Suggest a fix/enhancement

It may be im missing a configuration flag - please tell me! 🤣

If im not missing something in the configuration string : a simple fix would be to use the openapi json file's schema section to type matching to create stub results. If this is not something the current csharp generator does - could someone point me to where i could offer to add this via PR

Love this tool - thanks in advance!

Start with the CSharp generator entry point and the generated Unit Test Project template, then compare the emitted test methods with the OpenAPI schema types described in the issue. Reproduce with a C# generation command and verify that generated assertions are active and use valid schema-based values rather than TODO/null placeholders.