Retire or replace some test tools #9
Description
This issue is focused on discussing the needs of retire or replace some test tools used in the development process, exceptionally, Pactum, CucumberJS (frontend tier) and Cucumber (backend tier).
Initially, the idea behind to use this test tools as a manner to align the business goals proposed in the features and the product development. Starting from the common step definitions here, and specialising them in both frontend (here) and backend (here) tiers.
But, I'm not satisfied with the result that I expected in terms of test automation readability. I think the result that I obtained is so confusing to maintain in the next iterations. See these source code examples obtained here, here and draw your own conclusions.
So, I would like to listen your opinions about the needs of continuing using these tools for this project. If this a case of overengineering, and just the another test tools currently used to this project is enough. Or it's possible to improve these tests and it's a good ideia to maintain them.