Skip to main content

NDbUnit- Invalid object name

For our integration testing, we are using NDbUnit, a free open source .NET library for managing database state during testing. It ensures that our database is always in a consistent state before we start the execution of our tests. It uses an XSD schema to describe the database tables and an XML file can be used to provide the content.

After configuring everything, we initialized our database using following code

   1:  var mySqlDatabase = new NDbUnit.Core.SqlClient.SqlDbUnitTest(@"server=;user=;password=;initial catalog=");
   2:  mySqlDatabase.ReadXmlSchema(@"./Test.xsd");
   3:  mySqlDatabase.ReadXml("./Data.xml");
   4:  mySqlDatabase.PerformDbOperation(NDbUnit.Core.DbOperationFlag.CleanInsertIdentity);

But instead of populating our database with the correct values, we got an Invalid Object Name exception for each table. We found out that NDbUnit uses the default schema of the user specified in the connection string to look for the tables. So if you are using a different schema NDbUnit will not succeed in executing its scripts.



Something to keep in mind…

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more