Replies: 1 comment 9 replies
-
|
We don't set up the execution environment or the dependency resolution at all when running in .NET Core. That's done by VSTest. One way to verify this would be to port a single test to NUnit or MSTest and see if you get the same kind of result via |
Beta Was this translation helpful? Give feedback.
-
|
FYI, I have the following code in my Integration Test fixture... builder.ConfigureTestServices( services =>
{
// Recommended by Chapsas...doubt any present in this project, but just want here for reference
services.RemoveAll( typeof( IHostedService ) );
// few other 'safe' lines....
});Don't really recall why Nick Chapsas recommended this, but it was from one of his Zero to Hero training videos that I watched about Integration Testing. Is that line suspect at all? |
Beta Was this translation helpful? Give feedback.
-
|
For completeness and to make sure I'm doing things correctly.
public class GetTests : IClassFixture<ApiFactory>
{
private readonly ApiFactory factory;
public GetTests( ApiFactory factory )
{
this.factory = factory;
}
[Fact]
public async Task Get_ReturnsValidation_WhenParametersMissing()
{
// Arrange
await Task.Delay( 1 );
// Act
// Assert
}
}
[TestClass]
public class GetMSTests
{
private readonly ApiFactory factory;
public GetMSTests( ApiFactory factory )
{
this.factory = factory;
}
[TestMethod]
public async Task Get_ReturnsValidation_WhenParametersMissing_MSTest()
{
// Arrange
await Task.Delay(1);
// Act
// Assert
}
} |
Beta Was this translation helpful? Give feedback.
-
Believe it not (given my personal history), I have honestly zero experience testing ASP.NET Core apps in xUnit.net. 😞 |
Beta Was this translation helpful? Give feedback.
-
|
FastEndpoints definitely recommends us for integration testing: https://fast-endpoints.com/docs/integration-unit-testing#integration-testing I was able to follow their two step getting started: And then their tests ran: They are using their own customizations around fixtures, so this is their sample test class: using SayHello;
namespace Tests.SayHello;
public class Tests(App App) : TestBase<App>
{
[Fact, Priority(1)]
public async Task Invalid_User_Input()
{
var (rsp, res) = await App.Client.POSTAsync<Endpoint, Request, ErrorResponse>(
new()
{
FirstName = "x",
LastName = "y"
});
rsp.StatusCode.Should().Be(HttpStatusCode.BadRequest);
res.Errors.Count.Should().Be(2);
res.Errors.Keys.Should().Equal("firstName", "lastName");
}
[Fact, Priority(2)]
public async Task Valid_User_Input()
{
var (rsp, res) = await App.Client.POSTAsync<Endpoint, Request, Response>(
new()
{
FirstName = "Mike",
LastName = "Kelso"
});
rsp.StatusCode.Should().Be(HttpStatusCode.OK);
res.Message.Should().Be("Hello Mike Kelso...");
}
}and this is App: using Microsoft.AspNetCore.Hosting;
namespace Tests.SayHello;
public class App : AppFixture<Program>
{
protected override Task SetupAsync()
{
// place one-time setup for the fixture here
return Task.CompletedTask;
}
protected override void ConfigureApp(IWebHostBuilder a)
{
// do host builder configuration here
}
protected override void ConfigureServices(IServiceCollection s)
{
// do test service registration here
}
protected override Task TearDownAsync()
{
// do cleanups here
return Task.CompletedTask;
}
}Maybe that can send you in the right direction...? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot for peeking into it. I actually have no problem running FastEndpoints/XUnit together in other apis (I should have stated that). The problem only presented itself when I referenced .NET Framework. They asked for a sample repository and if you wanted to peek, you can see it here. I'll update this question if/when I resolve it. I'll have to see what they have going for fixture customization, sounds interesting. |
Beta Was this translation helpful? Give feedback.
-
I'm just starting the process of migrating an API to .NET Core. The Api needs to create a fire & forget job via Hangfire. The issue is that the job/delegate that is used to enqueue the Hangfire job needed to reference a .NET Framework assembly because that is not getting migrated yet.
I added the reference to my .NET Framework assembly and called via this line:
I've ran the API locally and submitted to it via Postman and the API successfully schedules that Hangfire job (and it executes) without issue.
However, when I try to run my integration tests against the api (and currently I'm not even testing this method, I just have a skeleton test project enabled for someone else to step in and start building tests), I get the following exception on all 3 of my endpoints that are tested.
I think this is something going on with xUnit (or my misuse) vs FastEndpoints since the Api works on its own??
Beta Was this translation helpful? Give feedback.
All reactions