Hello all, long time no see.
I’ve started looking at standardising our API test framework (C#).
We currently use a restsharp wrapper, allowing us to swap out when required to other http clients.
We use a service/repository model with NUnit and fluent assertions on top of that.
We decided against using BDD as it didn’t seem to sit very nicely, lots of storing scenario context variables etc. seemed to make invisible spaghetti code, has anyone had a better experience with this?
Thinking aloud…
-
I’ve had some ideas about using CURL somehow to allow our tests to be more maintainable, and able to directly base our tests off of documentation, maybe storing it in a CSV or DB…has anyone seen this done?
-
I’ve thought about just using postman + Newman, which we currently use for documentation, but I see limitations as our test environment data is unfortunately rarely predictable, so we currently seed/destroy data in test setup/teardown. The main drive for this is to make our tests more accessible to people who don’t do automation, has anyone had much success driving that?
-
Do I not need to make any changes?