You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi again
After doing the work for createBucket, the simple version, I noticed that there are at least some tests which are only testing for the correct, direct use-case. I think it'd be prudent to verify correct handling for e.g. incorrect method arguments. I realise that you don't want to emulate the AWS API entirely but I think some handling of incorrect args etc. would be very worthwhile.
Any thoughts?
Cheers
The text was updated successfully, but these errors were encountered:
I noticed you were quite thorough with the argument checking in the createBucket method. It's obviously a lot better to do that I think, although I suspect most people only use this at the moment to test /mock positive cases and not as an offline version of AWS that you can develop against. I'm afraid that extensive arg handling might get in the way, but if other people feel the need for it, it's something that should be included. Does that make sense?
Hi again
After doing the work for createBucket, the simple version, I noticed that there are at least some tests which are only testing for the correct, direct use-case. I think it'd be prudent to verify correct handling for e.g. incorrect method arguments. I realise that you don't want to emulate the AWS API entirely but I think some handling of incorrect args etc. would be very worthwhile.
Any thoughts?
Cheers
The text was updated successfully, but these errors were encountered: