Developer technologies | .NET | Entity Framework Core
A lightweight, extensible, open-source, and cross-platform version of the Entity Framework data access technology.
Getting error when running repository test after upgrading to .Net 6.0 from .Net Core 3.1 and EF Core 6 from EF Core 3.1 with a stored procedure
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 61%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
bsr7
1
Reputation point
Message:
System.NullReferenceException : Object reference not set to an instance of an object.
Stack Trace:
RelationalDatabaseFacadeExtensions.ExecuteSqlRawAsync(DatabaseFacade databaseFacade, String sql, IEnumerable`1 parameters, CancellationToken cancellationToken)
AuRepository.HasPermissionAsync(AppSession appSession, AppPermission permEntity) line 107
AuRepositoryTest.HasPermissionAsync() line 116
--- End of stack trace from previous location ---
Getting error when running repository test after upgrading to .Net 6.0 from .Net Core 3.1 and EF Core 6 from EF Core 3.1 with a stored procedure returning an int value. There is a service test that passes but the repository test is failing. Could you please advise on what could be going wrong with respect to repository test. Staying on EF Core 3.1 is not a solution as more unit tests failed for which the fix was to upgrade to EF Core 6
Developer technologies | .NET | Entity Framework Core
-
AgaveJoe 31,361 Reputation points2022-02-15T21:16:40.607+00:00 The null reference is the most common error is programming. It means the code is trying to access a member of an object but the object is referencing null. In other words, the object has not been created.
Simply run your code through the debugger to find the null object. It could be anything. Most likely the stored procedure is returning an empty result set and your code does not handle null properly. This is just a guess as I cannot see the code. Anyway, you have the lines of code that caused the exception. Review the code.
Keep in mind that executing a raw SQL script or a stored procedure is not a unit test. If the raw SQL has parameters then it is a matter of time until the test fails. The first thing you should do is verify that any parameter passed to the script or proc are still valid for the assertions being tested. You also want to verify the result set and testing assertions are still in sync. Typically unit tests use specific mock data for testing use cases because the mock data does not change like data in a table might.
-
bsr7 1 Reputation point
2022-02-15T22:12:03.013+00:00 Thank you for your response. This is a unit test project
-
Karen Payne MVP 35,606 Reputation points Volunteer Moderator2022-02-16T03:41:42.957+00:00 You should go through the following as there may be changes needed to your project and more so coming from 3.1.
Sign in to comment
Sign in to answer