Version 0.0.1
Is FakeXrmEasy a SaaS offering?
No. FakeXrmEasy is a software package that runs as part of a test process, most commmonly inside a Visual Studio application (or other development environments) and/or a CI/CD workflow.
How is FakeXrmEasy distributed?
FakeXrmEasy is distributed via the official Nuget feed. The official Nuget feed (nuget.org) is a Microsoft-owned package repository where Microsoft and the community publish software packages for download and consumption.
Does the software transfer any data to the internet (i.e. back to DynamicsValue or any other 3rd parties)?
No. FakeXrmEasy is a software application for unit testing and integration testing. As part of the unit testing process all the test data is short lived and resides in the memory of the process that runs the test suite. No external connections are needed or data is transferred for unit testing purposes.
If developers use FakeXrmEasy for integration testing purposes, (i.e. using a class called XrmRealContext), then they’ll need to provide a connection string to an On-Prem or Online Dataverse / CRM instance, depending on your use case. Users decide what connection string to use in that scenario. In this case, FakeXrmEasy is simply a wrapper to the CRM / Dataverse SDK and this connection is no different from other applications they are currently building and running.
Customers might enable our new licensing subscription mechanism (which is disabled by default). In that case, we provide interfaces to let customers decide where is the best place to store that information (most commonly their existing Azure Storage subscriptions).
Does FakeXrmEasy process customer’s personal data or Personal Identifiable Information (PII)?
FakeXrmEasy is not meant to be used to process any personal data. In fact, one of the many benefits is that allows building and testing your application logic with test / dummy data, which can (and should) be different from any production data. This avoids scenarios like when you restore from a backup and need to anonymise data for manual or integration testing purposes, for instance.
Following best software practices, users should take special care and make sure to NOT commit any sensitive or personal data while working in the test project.