Do you mean in aws-api?

Assuming you do, there is no specific support for doing that, so no docs. What are you trying to do?

^^ @U2J4FRT2T

I started with (aws/invoke (reify .... {:successId 42}) {:op :DoThing}) ;;=> {:successId 42} and I see that it's possible to mock out everything but i ran out of time I will try again this night. tnks 🙂

I still don't understand what you're trying to do. Why not just use a client as/is? Is this for testing?

Yep, for "offline" testing

Why not just use with-redefs?

I'm assuming that you're reifying ClientSPI, but that's internal and subject to (read: likely to) change. Until there's a documented seam for what you're doing you'll be safer with with-redefs (unless you're tests are concerned w/ thread safety, in which case 🤷 ).

Bit late but you can mock the http client api more easily, make sure to return an anomaly. Take a look at the tests for reference

That’s all internal as well. We’re working on a test double client (avoiding the word mock because we’re not going to explicitly support verification).

Unfortunately since there's no support for testing or documentation of the APIs in use, users must fend for themselves

Even something like "here's how you should test your code when using the library"

We’re working on something that looks like this right now.

(require '[cognitect.aws.client.test :as test]
         '[cognitect.aws.client.api :as aws])

;; implementation being tested
(defn do-something [s3-client]
  ;; if :response is bound to a value, invoke will return that value
  ;; if :response is bound to a funtion, invoke will return the return
  ;;    of that function
  (let [res (aws/invoke s3-client {:op :CreateBucket
                                   :request {:Bucket "a-bucket"}})]
    ;; do stuff with res
    ))

;; test using a stub
(let [test-s3-client (test/client {:api :s3})]
  (test/stub test-s3-client
             {:op :ListBuckets
              :response {:Location "a-location"}})
  (let [res (do-something test-s3-client)]
    ;; make assertions about res
    ))

;; test using a handler function
(let [test-s3-client (test/client {:api :s3})]
  (test/stub test-s3-client
             {:op :ListBuckets
              ;; op-map is the 2nd argument to `invoke`
              :response (fn [op-map]
                          ;; do stuff based on op-map
                          ;; then, return a value
                          {:Location "def"})})
  (let [res (do-something test-s3-client)]
    ;; make assertions about res
    ))

Actually, I just copied all that to a https://github.com/cognitect-labs/aws-api/issues/186#issuecomment-1205848703. Please respond there so we more easily find the conversation later.

cc: @UK0810AQ2 @U2J4FRT2T (sorry for the noise - but just want to make sure you see this - no urgency)

lgtm. Out of curiosity: why not test-s3-client (test/client {:api :s3 :stub (fn [op-map] ...)}) ? It would allow us to, for example, create things like :stub (in-memory-s3) or :stub (fs-s3 (io/file "..."))

How would that handle different s3 ops? i.e. if you invoke :ListBuckets and :CreateBucket in the course of the same test.

Of course, now that there will be a protocol, you can reify it any way you like.

I guess we could do it this way:

(test/client {:api :s3 :stubs {:ListBuckets {:Buckets [{:Name "bucket-1"}]} 
                               :CreateBucket (fn [op-map] ,,,)}})

The test client is on the `mcrmc/test-client` branch of https://github.com/cognitect-labs/aws-api. If you’d like to try it out,

git clone [email protected]:cognitect-labs/aws-api.git
git co mcrmc/test-client

Feedback welcome right here in https://github.com/cognitect-labs/aws-api/issues/186.

cc @UK0810AQ2 @U2J4FRT2T

Released in version 0.8.589. I’ll send out a more complete announcement later today.

I'm using it with S3 API to run in-memory tests in my app. It is a webservice + worker, that may turn into a SaaS when I have time

And it's working well for you? Any issues?