Can anyone advice me on a strategy to quickly create functional tests for a server that exposes an HTTP api against a thick client (think desktop app)?
My idea is to record http invocations between client and server in order to replay them during tests so I can test for server side effects such as "did the server create a backup of the data" etc. The server is written in Java, but the tests could/should be written using any programmatic language/tools as it needs not share libraries with the server.
I've looked into these alternatives:
charles proxy https://www.charlesproxy.com/
browsermob proxy: https://github.com/lightbody/browsermob-proxy
httpsnippet (generates code based on HAR recordings) https://github.com/Kong/httpsnippet
The problem with httpsnippet and Gatling was that they failed to replay the http post bodies even though they were stored in HAR files.
Aucun commentaire:
Enregistrer un commentaire