1 / 12

API testing myths debunked

Download Whitepaper from http://alm.parasoft.com/api-testing-myths API integrity plays a vital role in ‘The API Economy’. Yet many are confused about the kind of testing required to ensure secure and reliableAPIs. Discover the truth about API testing and the negative impact businesses face when APIs are not tested properly.

Parasoft
Download Presentation

API testing myths debunked

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. "5 Myths about API testing: There's more than meets the UI"

  2. APIs Everywhere and Here to Stay A few years ago, we entered the era of mobile computing But that came with some challenges: Apps connect devices to vast amounts of servers and data through complex APIs. How do you ensure that the APIs work as planned? Many devices, many networks and many connections. API failure means your apps fail, and your quality and reputation take a direct hit that flows to your bottom line API Testing reduces the business risk of faulty APIs

  3. Every App Has its API…to Test Enterprise apps rely on a myriad of internal, external and public APIs Testing APIs must include different networks, end-points and interfaces Test Scenarios Now Then The fact that an API is published does not decrease the test scenarios required; it increases test scenarios in all dimensions

  4. Myth #1 about Testing APIs 1 If it’s a published API, it’s been tested and guaranteed. No further testing required. # Just because an API is “published” does not mean that the API has been tested with anything, particularly your custom applications Public APIs, even the few with SLAs, are the responsibility of third parties – you may trust them, but you must verify them, with API Testing MIND THE GAP You cannot afford to overlook the gaps in testing APIs with your applications

  5. Myth #2 about Testing APIs 2 We’ve tested the API through our application’s graphical user interface testing. # Tested through the GUI of your applications does not mean you have fully tested the API and its other interactions Assuming that you’ve tested the API from the GUI means on average 10% test coverage GUI tests are extremely fragile and are not designed to exercise the integration layer

  6. Myth #3 about Testing APIs 3 Our GUI testers can exercise the API directly… It seems pretty straightforward. # While direct testing may provide validation of connectivity, it will not exercise the end-to-end logic of the API and its interactions with dependent systems You thought you could manage simple transactions… Composite applications are dependent upon multiple transactions End-user experience is dependent upon everything working together flawlessly, not a single message transaction …until you realized the API was more complicated (with multiple operations and elements)

  7. Myth #4 about Testing APIs 4 End-to-end tests are not feasible, because there are too many dependencies involved. # Testing modern composite applications requires access to an average of 30 dependent applications (APIs, mainframes, web services and other systems dependencies), yet only 20% can be accessed easily for testing This complexity does not mean end-to-end testing cannot be performed Technologies like service virtualization (test environment simulation), when coupled with API Testing, provide for comprehensive testing across all application dependencies

  8. Myth #5 about Testing APIs 5 APIs that were tested once and worked will continue to work as long as the API hasn’t changed. # Methodologies like Agile Development require that application logic changes, improves and evolves In order to ensure the integrity of the API, any material change to the API requires a re-validation of the API and its system dependencies Because you tested this… Creating a regression test suite that exercises dependent APIs consistently is required for API integrity …doesn’t mean you’ve tested this!

  9. The Costs of not Testing APIs If software is the interface to your business, then the customer’s experience is only as good as the weakest link in your software Switching costs for software are at an all-time low; subscription models and common interfaces mean that loyalty has to be earned with quality and innovation If you’re leveraging APIs to enhance your customer’s experience, you must ensure that the APIs can meet or exceed your business expectations

  10. Parasoft API Testing: Real Results Parasoft API Testing has helped accelerate and transform application testing for many leading companies and agencies

  11. Parasoft Leadership Over 7,000 companies trust Parasoft Rock-solid, profitablesince the 1990s IP war chest with 32 defect prevention patents SHIFT LEFT Test early, test often, with the leader in Continuous Testing: Parasoft Service Virtualization API Testing Development Testing

  12. Download Whitepaper www.parasoft.com

More Related