Skip to content

Commit ef3b1e9

Browse files
committed
Role checks with respect that nav prop is null 4 SQLite
1 parent 610001a commit ef3b1e9

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

Wissance.WebApiToolkit/Wissance.WebApiToolkit.Tests/Controllers/TestBulkCrudControllerWithDynamicAutoManager.cs

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,16 @@ public async Task TestReadMany()
2626
string pagedDataStr = await resp.Content.ReadAsStringAsync();
2727
Assert.True(pagedDataStr.Length > 0);
2828
OperationResultDto<PagedDataDto<RoleDto>> result = JsonConvert.DeserializeObject<OperationResultDto<PagedDataDto<RoleDto>>>(pagedDataStr);
29-
// TODO(UMV): check very formally only that ReadAsync returns PagedData wrapped in OperationResult
3029
Assert.NotNull(result);
3130
Assert.True(result.Success);
31+
// TODO(UMV): These test works with SQLite in memory db therefore Navigation property (virtual) does not contains related Users, but actually all Users have roles
32+
IList<RoleDto> expected = new List<RoleDto>()
33+
{
34+
new RoleDto() {Id = 1, Name = "Administrator", Users = new List<int>()},
35+
new RoleDto() {Id = 2, Name = "Office manager", Users = new List<int>()},
36+
new RoleDto() {Id = 3, Name = "Corporation slave", Users = new List<int>()}
37+
};
38+
RoleChecker.Check(expected, result.Data.Data);
3239
}
3340
}
3441

0 commit comments

Comments
 (0)