So my team went over our latest project today, and we're building the APIs for a mobile app (mobile app itself will be outsourced). I've never tested this sort of thing before, so any tips to help with the testing would be much appreciated!
Some notes:
I'm the QA Analyst (I do the plans, cases, test strategy, etc) and do the manual testing. Is there even really any manual testing to do with just APIs?
I've pinpointed soapui and postman as potential test tools. Any others that are useful? Pros/cons?
Our automation engineer is planning to bypass Selenium interface and just work with C# directly with the APIs. Any pitfalls, things to consider, ideas, tips?
Any common stumbling blocks, errors, edge cases that come up with API testing?
Thanks in advance!
01-29-2021 02:37 AM
The first step to API testing is to actually do it. Without good tests, it’s impossible to have full confidence in your API’s behavior, consistency, or backward compatibility.
As your API grows in complexity, it will become important to organize your tests so they make sense and can be found easily. I suggest that you by resource, test suite, and workflows myaarpmedicare.com
02-04-2021 02:29 AM
You can search them online.
11-03-2021 03:28 AM