I am concerned in a microservices based mostly utility. I am attempting to use the BDD course of for this. I want a suggestion how you can apply this course of accurately given one of these structure. It is strongly recommended to keep away from or hold at minimal degree the end-to-end exams that span throughout many microservices. I agree with that.
From my standpoint, staying away from end-to-end exams implies that we do not have executable specs (one of many bdd advantages) for the use instances that span a number of providers. As an alternative we have now solely service degree specs.
Is my understanding right?
Right here is an instance. Say, I’ve a e-commerce system and I must implement the characteristic:
Including a product to the buying cart.
When discussing this with the shopper, we put down the next situation:
Given I am logged in And I seek for the e book "BDD in Motion" And I recognized the required e book After I add the merchandise to the buying cart Then I see the merchandise added to my buying cart
This use case spans the next microservices: Safety, Product Catalog, Purchasing Cart.
Therefore the query – how do I implement the above buying cart characteristic following the BDD course of?
- Ought to I automate the above characteristic file? In keeping with the already talked about suggestion, I ought to keep away from end-to-end exams spanning a number of microservices. Does it imply that the above story stays not executable?
Ought to I am going straight to the Purchasing Cart Service and write a specification for it, avoiding the pointless Givens from the above story?
After I add an merchandise to the Purchasing Cart
Then I see the merchandise added to my buying cart