Hi all,
In the previous and current sprint we have a few tickets to introduce performance tests for existing endpoints. Currently we have one ticket (example: OLMIS-3211) for:
1. creating performance tests,
2. checking (if needed) why those endpoints does not fit requirements
3. improving endpoints to fit requirements
I think we could split this kind of tickets into three tickets instead of having one. One thing is to show that there is a progres in tickets. Currently tickets are in
in progress or in
review columns by several days because endpoints in most cases do not pass requirements. Also it always better to have few smaller tickets that are focused on single thing (like adding tests) in the sprint instead of one big ticket that have everything.
Another thing is that sometimes is very hard to find a good way to improve endpoints. For example the delete inventory item endpoint has only three steps:
1. find object in database
2. check permissions
3. delete object from database.
In the ticket this endpoint should be executed in 500ms but p90 is equal to 635ms (taken from the last performance execution on CI).
So sometimes investigation part will require starting a discussion on dev group about how we would like to improve some part of codes. I think permission strings are good example here.
If this approach does not sound as a great idea maybe we could have rule: one endpoint one performance test ticket.
What do you think about that?