Minimal APIs at a glance in .NET 6

Re:Minimal APIs at a glance in .NET 6 by andix on Monday September 13, 2021 @11:57AM (#28513104)

But there are multiple ways to return a file type. There are also multiple ways to define a route. You can name the method item[] GetItem() or use attributes [HttpGet] item[] Items().

If you do integration testing, you verify what will be returned in the end to the caller over http. For that you don’t need selenium. Just use testserver, it’s just a few lines of c# Code.

[ Parent | on HN ]

Re:Minimal APIs at a glance in .NET 6 by Jenk on Monday September 13, 2021 @01:18PM (#28514063)

Unit testing and integration testing are not mutually exclusive. I use both. I also want the feedback from tests/build of what I am developing to be as immediate as possible. Failing early with a test that takes a second to spool and run with a message like "expected File got Content" or whatever is more valuable than waiting for a much longer test for the same (or more obscure due to depth of stack that will need a debug session) message.

TL;DR: Running an entire webstack to test trivial things is waste.

> Just use testserver, it’s just a few lines of c# Code.

Orthoganol metric is orthoganol.

    await Task.Delay(TimeSpan.FromHours(1));

Is just one line of c#. Doesn't meant it's going to run any quicker.

[ Parent | on HN ]

Re:Minimal APIs at a glance in .NET 6 by moogly on Monday September 13, 2021 @12:52PM (#28513741)

TestServer is great. And if you use Alba[1], it gets even better.

[1]: https://jasperfx.github.io/alba/guide/hosting.html

[ Parent | on HN ]