Cyno, cyno@programming.dev

Instance: programming.dev
Joined: 2 years ago
Posts: 11
Comments: 10

RSS feed

Posts and Comments by Cyno, cyno@programming.dev

The problem is obvious however, most people just want a quick and easy component library and don’t care about stuff like that. I often fall into that group too, because making new components from scratch is boring and annoying and then often end up looking worse with fewer features anyway than if you just copy pasted the messy shadcn amalgamation



I haven’t used them much recently but aren’t vue and svelte very similar in terms of difficulty and philosophy?


nah im good lol

bruno seems decent


oh damn i had no idea, thanks! “help” is not where i expected to find it lol


I really wish gimp had a command palette, kinda like the Ctrl+Shift+P thing in VSCode. As a beginner in gimp I often know approximately what I want to do, but not how to find that thing and just being able to type “crop”, “scale”, “add layer” and have it happen would be much easier than having to look for it through various menus.


I still don't think it's nearly as convenient as being able to just see the changes side by side and click the one you want (or both). You can even easily modify the final outcome in the 3rd preview panel, in case you need to do a quick fix after a conflict resolution.


You are probably right and I just misunderstood fixtures / collections and how they work. I am now trying to configure it using postgres testcontainers and just letting each test create its own but facing a bunch of other issues so not even sure how this works anymore, seems like every tutorial has a different approach. Some just put all the code for creating containers in the setup/dispose of the test class itself instead of trying to be smart with the WebApplicationFactory fixtures and maybe I just end up doing that


My first intent was to just have one local sqlite test db that would get reset to empty state before the tests run (EnsureDeleted+EnsureCreated), and then they all run concurrently on it. It sounded simple to setup and simple enough for my small crud app that only had a few tests.

My second intent was for the framework to create a new in-memory sqlite db for each test so I could fix the problem with tests failing when I'd run all of them at the same time, presumably because they all referenced the same db.

I am currently trying to complicate my life further in the hopes it helps with this by using a postgres database instead, and then in the IntegrationTests project I'm using TestContainers to get a PostgreSqlContainer. I am currently suffering because of some change I made so my tests aren't even being found anymore now, despite being listed in the test explorer when I run them I get "Test discovery finished: 0 Tests found" in output. Honestly I think I'm just gonna give up integration testing like this, it's been a complete waste of time so far.

Dunno what else I could say about my project that is relevant, it's a standard webapp crud with 2 controllers and the integration tests projects has facts like this. Very basic stuff I'd say. Unit tests are a separate project and will just be for simple method checks, no mocking (or at least as little as possible)


Configuring a DbContextFactory in the WebAppFactory instead of a DbContext breaks my services, they can't resolve DbContext anymore so all requests from my test classes fail. Either I misunderstood you or how this works, but it makes sense - I need to properly fix the injectable DbContext so it fixes it everywhere and not just add a DbContextFactory for test classes while the actual code still injects a DbContext.

Configuring the DbConnection service scope as Transient didn't change anything.

I might consider efficiency and speed later but for now I'd be happy to just get it working on this simple CRUD app with 2 test classes, I've spend hours trying various google solutions and I'm a bit frustrated there is no simple guide for something that should be so seemingly simple at this point.


RSS feed

Posts by Cyno, cyno@programming.dev

Comments by Cyno, cyno@programming.dev

The problem is obvious however, most people just want a quick and easy component library and don’t care about stuff like that. I often fall into that group too, because making new components from scratch is boring and annoying and then often end up looking worse with fewer features anyway than if you just copy pasted the messy shadcn amalgamation



I haven’t used them much recently but aren’t vue and svelte very similar in terms of difficulty and philosophy?


nah im good lol

bruno seems decent


oh damn i had no idea, thanks! “help” is not where i expected to find it lol


I really wish gimp had a command palette, kinda like the Ctrl+Shift+P thing in VSCode. As a beginner in gimp I often know approximately what I want to do, but not how to find that thing and just being able to type “crop”, “scale”, “add layer” and have it happen would be much easier than having to look for it through various menus.


I still don't think it's nearly as convenient as being able to just see the changes side by side and click the one you want (or both). You can even easily modify the final outcome in the 3rd preview panel, in case you need to do a quick fix after a conflict resolution.


You are probably right and I just misunderstood fixtures / collections and how they work. I am now trying to configure it using postgres testcontainers and just letting each test create its own but facing a bunch of other issues so not even sure how this works anymore, seems like every tutorial has a different approach. Some just put all the code for creating containers in the setup/dispose of the test class itself instead of trying to be smart with the WebApplicationFactory fixtures and maybe I just end up doing that


My first intent was to just have one local sqlite test db that would get reset to empty state before the tests run (EnsureDeleted+EnsureCreated), and then they all run concurrently on it. It sounded simple to setup and simple enough for my small crud app that only had a few tests.

My second intent was for the framework to create a new in-memory sqlite db for each test so I could fix the problem with tests failing when I'd run all of them at the same time, presumably because they all referenced the same db.

I am currently trying to complicate my life further in the hopes it helps with this by using a postgres database instead, and then in the IntegrationTests project I'm using TestContainers to get a PostgreSqlContainer. I am currently suffering because of some change I made so my tests aren't even being found anymore now, despite being listed in the test explorer when I run them I get "Test discovery finished: 0 Tests found" in output. Honestly I think I'm just gonna give up integration testing like this, it's been a complete waste of time so far.

Dunno what else I could say about my project that is relevant, it's a standard webapp crud with 2 controllers and the integration tests projects has facts like this. Very basic stuff I'd say. Unit tests are a separate project and will just be for simple method checks, no mocking (or at least as little as possible)


Configuring a DbContextFactory in the WebAppFactory instead of a DbContext breaks my services, they can't resolve DbContext anymore so all requests from my test classes fail. Either I misunderstood you or how this works, but it makes sense - I need to properly fix the injectable DbContext so it fixes it everywhere and not just add a DbContextFactory for test classes while the actual code still injects a DbContext.

Configuring the DbConnection service scope as Transient didn't change anything.

I might consider efficiency and speed later but for now I'd be happy to just get it working on this simple CRUD app with 2 test classes, I've spend hours trying various google solutions and I'm a bit frustrated there is no simple guide for something that should be so seemingly simple at this point.