| ▲ | vmg12 2 hours ago | |
Why not just write to the db? Just make every test independent, use uuids / random ids for ids. | ||
| ▲ | mystifyingpoi an hour ago | parent | next [-] | |
> Just make every test independent That's easier said than done. Simple example: API that returns a count of all users in the database. The obvious correct implementation that will work would be just to `select count(*) from users`. But if some other test touches users table beforehand, it won't work. There is no uuid to latch onto here. | ||
| ▲ | 2 hours ago | parent | prev | next [-] | |
| [deleted] | ||
| ▲ | vladraz 41 minutes ago | parent | prev | next [-] | |
Frankly this is the better solution for async tests. If the app can handle multiple users interacting with it simultaneously, then it can handle multiple tests. If it can’t, then the dev has bigger problems. As for assertions, it’s not that hard to think of a better way to check if you made an insertion or not into the db without writing “assert user_count() == 0” | ||
| ▲ | szundi 2 hours ago | parent | prev [-] | |
[dead] | ||