Which approach or should I say framework is better and which are let say 3 facts you should consider when making final decision?
Which approach or should I say framework is better?
I don't think you can compare them just like that when you don't mention any context, any goals you might have, what you want to achieve with the tool, how big your project is, who is on the team, and many more.
Which are let say 3 facts you should consider when making final decision?
Some things I'd consider:
- who will participate in the project, what are their (including mine) skills (can they handle the tool, if not, will there be some time for learning?)
- how big the project is - http clients are great for exploratory testing and tend to be a bit clumsy when it comes to managing many endpoints, a lot of test data, or when you want to reuse some parts (code)
- what intergations we need - how well the tool supports CI/CD pipelines, reporting, ...
- how easy it will be for someone completely new to take over - it's easier to start working with a http client than learn to code and then use a library like Rest-assured
The best setup is when you have enough space to fail. If you're not under a lot of pressure, pick one of the two, start using it and if it doesn't prove efficient on the project, change it. Yes, there'll be some rework, but you have to learn somehow, don't you?