mirror of
https://github.com/ilyakooo0/roboservant.git
synced 2024-11-25 21:55:06 +03:00
1.5 KiB
1.5 KiB
extensions/todo
- add some "starter" values to the store
- there may be a JWT that's established outside the servant app, for instance.
class Extras a where extras :: Gen [a]
- default implementation
pure []
- selectively allow some types to create values we haven't seen from the api.
newtype FirstName = FirstName Text
, say.
- default implementation
- break down each response type into its components
- if i have
data Foo = FBar Bar | FBaz Baz
- an endpoint
foo
that returns aFoo
- and an endpoint
bar
that takes aBar
- I should be able to call
foo
to get aFoo
, and if it happens to be anFBar Bar
, I should be able to use thatBar
to callbar
.
- if i have
- better handling of properties to be verified
- some properties should always hold (no 500s): this already works.
- to-do: there may be some other properties that hold contextually
- healthcheck should be 200
- test complex permissions/ownership/delegation logic - should never be able to get access to something you don't own or haven't been delegated access to.
other possible applications
-
coverage
- if you run the checker for a while and
hpc
suggests you still have bad coverage, your api is designed in a way that requires external manipulation and may be improvable.
- if you run the checker for a while and
-
benchmarking
- we can generate "big-enough" call sequences, then save the database & a sample call for each endpoint that takes long enough to be a reasonable test.
- from this we can generate tests that a given call on that setup never gets slower.