Getting Started With API Functional Testing With BlazeMeter

ICYDK: As we move towards more Agile Shift-left software development processes like continuous integration and delivery, developers need to be able to quickly and efficiently run tests during the entire delivery cycle.

One downfall to UI functional tests is they are slow. This makes them less than ideal for letting developers know quickly if their code has broken the latest build or not. API functional tests, on the other hand, tend to be faster. API functional tests also tend to run more reliably than GUI functional tests because changes in the user interface usually occur more frequently then changes on the API level. Therefore GUI tests tend to be more brittle than API level tests. https://goo.gl/G4kDcN #DataIntegration #ML

3 Reasons Your API Might Fail

APIs. You depend on them, but can you always trust them to work as advertised? The truth is that APIs can fail, and even when they don’t fail, they can perform in ways that are less than adequate. When that happens, your application may be left hanging, or worse yet, it may crash. What kind of failures are we talking about, and what can you do about them?

First, though, consider what an API does. It provides a way for a programmer to communicate with an external application or service, and to ask that application to do something. You may or may not know what the other program does internally with your data and your request, but as long as everything works correctly, all you need to know is how to use the API. But that is not enough to ensure that APIs perform adequately. https://goo.gl/CnRmHu #DataIntegration #ML