sunnyp410

PostsComments

CC#

•Created by saiss. on 1/22/2023 in #help

❔ Testing API's in .NET

So I would start off with the basics by looking at the unit testing strategies that your new job desires. Meaning do they do TDD when writing unit tests? What unit test naming strategies they use? Once you got that info I would start doing some TDD on your feature work or pair with someone to get an idea. Then I would move onto Integration testing which test a certain component or example calling another API or databases etc. Should be simple and straight forward to write. Again pair programming is key :). Finally Service Tests (E2E) which should check all of your code within an environment. This can be done using WAF or postman api scripts Acceptance Tests - This is just a bonus I would not recommend this as your E2E test should cover this. In a nutshell its BDD. Performance Test is a bonus this can be run within a seperate pipeline which can be within another container. Have a look into these two :- * https://k6.io/ * https://nbomber.com/docs/overview/

6 replies

CC#

•Created by stevon8ter on 1/20/2023 in #help

❔ Which ORM? [query sys.objects, ...]

I would go for Dapper. Used it in may codebases, easy and lightweight to use. It kinda reminds me back in the ADO.NET days 🙂

14 replies

CC#

•Created by linqisnice on 1/14/2023 in #help

❔ What architecture is recommended for a new (to be enterprise) project?

If the project grows, you may want to think about splitting logic into another service or having some sort of common lib that takes in common functionality.

17 replies

CC#

•Created by linqisnice on 1/14/2023 in #help

❔ What architecture is recommended for a new (to be enterprise) project?

Clean Architecture with DDD/CQRS principles.

17 replies