| || |
Testing Web APIs
I see "Testing Web APIs." on many requirements.
I have called Test Director\QC and probably soon ALM APIs from VBA, VBScript and QTP. Would Web APIs be something close to what I was doing? Is Web API testing for checking that the APIs work correctly?
Is this the part of UFT that makes it Unified? What are the other things that UFT does that makes it Unified?
I'm not sure if these should be two separate questions or if they are related.
The most popular tool for api testing is SOAPUI.
But you can test APIs using almost anything.
Generally most people will opt for using a unit testing framework in the same language as their developers so the developers can run the tests themselves before they check in code.
You can even test API's using a load testing tool. That's basically the main thing they do, record and playback requests very fast and monitor the error rate. If you run a load testing tool with only 1 virtual user, you're basically doing a functional API test.
When we say "Testing Web APIs" when looking for testers we would usually mean manual tests. The automated tests would be written most of the time by developers. Than the testers would use SoapUI and tools like that to see what the devekopers might have missed. If the find something, they feed back to the developer so that they can create additional automated tests to cover the missing bits. Why we do not like when testers write tests? Because tests need to be SOLID, DRY, YAGNI, etc. And it takes years of hands on software development to understand what those really mean. So the tester without a solid software development background is unlikely to write better maintainable tests than the software developer.