GIS Converter -Console App -Tests Coverage

Your current tests don't verify the SetLogger method at all. You need to test scenarios like invalid log paths, missing directories, case-insensitive log levels, and what happens when logging initialization fails.
You need comprehensive tests for malformed arguments, empty strings, special characters, and boundary conditions.
You test some exit codes but not all paths systematically.
Your integration tests only check whether files exist, not whether they contain valid data.

I have created some tests to illustrate. Use them as references to expand your own test suite.

LoggingTests.cs.txt

ArgumentParsingTests.cs.txt

ExitCodeTests.cs.txt

OutputValidationTests.cs.txt

Happy holidays.

Dani_S 5,131 Reputation points

2025-12-18T12:28:59.96+00:00

Hi Michel,

1.Some tests are not passed.

Tests Errors.txt

2.Files:

Console App Code

# GisConverter ConsoleApp.txt

Console App

Program.txt

Console App Tests Code

# GisConverter.TestsApp.txt

Console App Tests

README.md.txt

ArgumentParsingTests.cs.txt

ExitCodeTests.cs.txt

LoggingTests.cs.txt

OutputValidationTests.cs.txt

ProgramIntegrationTests.cs.txt

ProgramTests.cs.txt

Thank you very much for your help!!!
Michael Le (WICLOUD CORPORATION) 7,020 Reputation points Microsoft External Staff Moderator

2025-12-19T02:34:28.07+00:00
Hello @Dani_S ,

Let me address each issue:

Exit code inconsistency for help commands

Your tests are expecting help commands to return exit code 1, but your Program.cs is actually returning 0. If you look at this section of your code:

if (args.Length == 0 || args[0] == "help" || args[0] == "--help" || args[0] == "-h") { ShowHelp(); return (int)ExitCode.Success; // This returns 0 }

Change these assertions from Assert.Equal(1, exit) to Assert.Equal(0, exit) in both ArgumentParsingTests.cs and ExitCodeTests.cs.

Invalid target format test

The test Run_InvalidTargetFormat_ReturnsAppError is getting exit code 2 instead of the expected 1. Both are valid failure scenarios, so update your test to accept either:

var exit = GisConverter.ConsoleApp.Program.Run(args); Assert.True(exit == 1 || exit == 2, $"Expected exit 1 or 2, got {exit}");

Aspose evaluation limit issue

"Evaluation limit exceeded: 15 files per hour."

This is coming from Aspose, not your code.

You have two options to fix this:

First option - apply a valid Aspose license. Make sure your AsposeLicenseManager.ApplyLicense() is working correctly in your test setup.

Second option - skip tests that require actual conversion when the license isn't available. Add a helper method to your test classes:

private bool IsAsposeLicensed() { return !string. IsNullOrEmpty(Environment. GetEnvironmentVariable("GISCONVERTER_ASPOSE_LICENSE_PATH")); }

Then at the start of tests that do real conversions, add:

if (!IsAsposeLicensed()) { return; // Skip test if Aspose isn't licensed }

Or you can check the output for the evaluation limit message and skip conditionally:

var exit = GisConverter.ConsoleApp.Program.Run(args); if (exit != 0) { var output = _outWriter.ToString() + _errWriter.ToString(); if (output.Contains("Evaluation limit exceeded")) { return; // Skip - hit Aspose evaluation limit } Assert.True(false, $"Conversion failed: {output}"); }

Logging warning not showing in stderr

The test Run_WithInvalidLogPath_PrintsWarningToStderr expects a warning but stderr is empty. The problem is that your logging library might be automatically creating directories, so the "invalid" path isn't actually failing. Use a truly impossible path in your test:

var invalidLogPath = Path.Combine("Z:\\NonexistentDrive\\", "subdir", "test.log");

Answer 2

Q&A Assist

AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

To ensure that your GIS Converter Console App has adequate test coverage, you can utilize code coverage tools available in .NET. Here are some steps and tools you can consider:

Use Code Coverage Tools: .NET includes a built-in code coverage data collector that generates a binary .coverage file. You can use this file to create reports in Visual Studio. Additionally, you can use the dotnet-coverage tool to convert the binary coverage results to a human-readable format.
Coverlet: This is an open-source alternative that generates test results as human-readable Cobertura XML files. Ensure your unit test project has the appropriate package dependencies to use Coverlet.
Viewing Coverage Results: You can view the coverage results in the Code Coverage Results window in Visual Studio. This window allows you to see which parts of your code are covered by tests and can help identify any missing tests.
Merging Results: If you have multiple test runs, you can merge the results to get a comprehensive view of your test coverage.
Exporting Results: You can export the coverage results to XML format for easier sharing and analysis.

By following these practices, you can assess whether you have added all necessary tests and identify any areas that may require additional testing.

Dani_S 5,131 Reputation points

2025-12-17T08:22:15.78+00:00

Hi Michel,

Can you please answer?

Thanks in advance,
Dani_S 5,131 Reputation points

2025-12-17T11:41:42.5633333+00:00

I added the wrong Program.cs, here is the correct one.

Porgram.txt
Dani_S 5,131 Reputation points

2025-12-19T04:18:28.7066667+00:00

Hi Michel,

1.I fixed all tests and all passed now.

2.I updated all remarks and README.md files.

3.Regarding Aspose evaluation limit issue I used the first option:

"Apply a valid Aspose license. Make sure your AsposeLicenseManager.ApplyLicense() is working correctly in your test setup."

4.How to setup license in Tests project, will be discussed in

https://learn.microsoft.com/en-us/answers/questions/5666892/gis-converter-unit-tests-projects-set-aspose-licen

Thank you very much for your help.

You are very professional programmer.

Share via

GIS Converter -Console App -Tests Coverage

1 additional answer

Your answer