❔ How much should a single test cover?
I've just finished making a integration test for some goods in functionality. So when we receive a delivery in the warehouse the operator will input how many of each item they accept or reject,
The test checks that when a item is accepted, it is added to stock details and if all items on the purchase order are accounted for it updates the status. It also check that when a item is rejected a new PO is raised and the status is set to rejected.
That's all fine.
Now there is also the possibility that a delivery being booked in will be linked to a job,. This is when we have sub contracted another company to do some work for us and they have delivered the finished product.
When that happens, the normal book in stuff above happens but then also the linked job will be updated.
That job update functionality is a beast of it's own. So the event chain for it is fired from the book in method if needed and I can test all of the stuff has been updated correctly.
So what I am wondering is... if my book in test is checking all of that job update stuff already. Is it worth making another test for that stuff or should I not bother testing it within the book in methods and just create specific tests for the job updates?
1 Reply
Looks like nothing has happened here. I will mark this as stale and this post will be archived until there is new activity.