nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unit testing ArcGIS Runtime SDK for .NET

JuhoVainio

As far as I know, the current ArcGIS Runtime SDK for .NET cannot be unit tested because we simply cannot create new instances from the classes and thus cannot mock any return values from queries. The older ArcObjects library was easier to mock, because every class also had an interface assigned to it.

Currently this is a bit of a problem because we cannot create unit tests for ANY functionality that uses any of the ESRI's classes (or they become integration tests).

Is ESRI going to upgrade the SDK so that unit testing might be possible in the near future?

Find more posts tagged with

Accepted answers

All comments

FridjofSchmidt

Juho,

There is now an idea at ideas.arcgis.com: Support unit testing in ArcGIS Pro and ArcGIS Runtime .NET SDKs. If this seems important to you, please promote the idea.

I don't consider this question answered. Apparently, Esri uses MS Fakes internally for writing their unit test, i.e., they can isolate their code from dependencies by using Shims. However, MS Fakes is only available for the Enterprise edition of Visual Studio. Both the ArcGIS Runtime SDK .NET and the ArcGIS Pro SDK support all editions of Visual Studio.

JuhoVainio

Thanks for taking the time to answer. I hope you can improve the SDK's unit testing capabilities in the future.

SomeGISGuy

We are using Visual Studio's unit test framework and nUnit.

Wrt to FeatureTable - it is an abstract class and subclasses are implemented at the native level and therefore we can't support subclassing this directly. This actually goes for quite a lot of the classes, and why you see a lot of sealed or non-creatable classes. Other cases, it's to properly convey that data isn't editable and is kept read-only.

JuhoVainio

Thanks for the quick reply. It would be great if you could share an example solution that would contain some example unit tests. What testing framework are you using by the way? We're using Moq.

Also about mocking server response: currently it's quite impossible to unit test our data access layer, because for example FeatureTable's constructor is internal. So I'm hoping you'd come up with some improvements on that later.

And you're absollutely correct about the interface hell, it wasn't very convenient

SomeGISGuy

Most of the API can be unit tested (we have thousands of unit tests ourselves). You are correct that some classes - mainly data coming from the server are not creatable or settable - the API is strict on mimicking the nature on the server (ie some things just aren't settable) and we'd like to keep it that way. We did have a prototype early on to mock server responses, so that you can mock results but had to be pulled out. We do want to revisit that in the near future (note: this isn't mocking classes but mocking the server). You could accomplish this with a proxy though.

We don't want to get into the interface hell that COM has forced onto ArcObjects. For example we don't want to find ourselves with 7 polyline interfaces in the future. It's just not a pretty API to work with in the long run.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.