I know implementing the automation pyramid is hard,
And to a large extend, is not a problem with just testing practices either..
I’ve seen teams where products don’t have contracts written up properly (API contracts / JSON schemas)
Back end services are not designed for anyone other than the developer to consume..
Such places do make it hard to implement the pyramid, i.e. 70 – 80% tests at the back end,
The solution: The whole team work on developing those contracts, and then write tests for those contracts..
Easier said than done, but until you don’t have that, testing isn’t going anywhere.
#QsDaily #Automation #Testing #ApiAutomation #AutomationPyramid
What do you mean by conttact written up? Can you give an example, please?
For API’s the service provider should write a ‘contract’ (behavior) of the format of requests to send to the API, and what will be sent back in response. Essentially requirements of how the API will behave. These are called contracts, because it’s an agreement between the service provider and user of how the API will behave.
Documenting the ‘contract’ can be done through a wiki / confluence page, but best practice dictates to use API documentation tools like swagger, this was the contract is documented from the actual code, not a static document which have to keep up to date all the time.