Meta tags:
Headings (most frequently used words):
testing, api, contents, overview, gui, and, test, automation, types, of, see, also, references,
Text of the page (most frequently used words):
#testing (118), and (52), the (49), api (43), software (20), apis (20), with (19), test (19), this (17), for (13), security (11), gui (11), that (10), automation (9), edit (9), are (9), tests (9), web (8), system (8), wikipedia (7), development (7), application (7), from (6), user (6), box (6), used (6), can (6), page (5), links (5), short (5), see (5), performance (5), types (5), agile (5), functional (5), find (5), type (5), services (5), contents (4), search (4), about (4), under (4), all (4), reliability (4), interface (4), also (4), integration (4), how (4), 2014 (4), checks (4), vulnerabilities (4), programming (4), issues (4), identify (4), fix (4), involves (4), determine (4), expected (4), include (4), devops (4), such (4), iso (4), tools (4), hide (4), move (4), sidebar (4), languages (3), view (3), code (3), using (3), multiple (3), articles (3), dead (3), external (3), wayback (3), black (3), smoke (3), random (3), link (3), 2019 (3), machine (3), 2015 (3), actions (3), bugs (3), its (3), performs (3), maintain (3), transactions (3), unexpected (3), input (3), requirements (3), cases (3), performed (3), these (3), their (3), release (3), end (3), being (3), message (3), part (3), changes (3), standards (3), management (3), main (3), toggle (2), table (2), mobile (2), developers (2), contact (2), privacy (2), policy (2), terms (2), use (2), was (2), july (2), cs1 (2), maint (2), names (2), authors (2), list (2), description (2), different (2), wikidata (2), https (2), stress (2), model (2), usability (2), execution (2), continuous (2), compatibility (2), unit (2), acceptance (2), levels (2), cite (2), ieee (2), what (2), scrum (2), adrian (2), bridgwater (2), dobb (2), journal (2), learn (2), against (2), brittle (2), defects (2), august (2), gartner (2), amy (2), reichert (2), searchsoftwarequality (2), archived (2), third (2), party (2), forrester (2), beyond (2), references (2), service (2), virtualization (2), automated (2), correctly (2), components (2), assess (2), design (2), business (2), logic (2), attackers (2), penetration (2), prevent (2), data (2), evaluates (2), handle (2), high (2), inputs (2), request (2), response (2), any (2), errors (2), error (2), detection (2), fixed (2), runtime (2), results (2), related (2), validation (2), they (2), meet (2), expectations (2), functionality (2), other (2), without (2), soap (2), includes (2), single (2), endpoints (2), tester (2), output (2), not (2), most (2), working (2), potential (2), artificial (2), intelligence (2), reasons (2), recommended (2), teams (2), level (2), edge (2), fast (2), feedback (2), loops (2), frequent (2), layer (2), less (2), cycles (2), considered (2), commonly (2), sent (2), over (2), formats (2), 8583 (2), well (2), directly (2), team (2), overview (2), because (2), interfaces (2), computer (2), engineering (2), modeling (2), tdd (2), deployment (2), appearance (2), upload (2), file (2), history (2), read (2), article (2), log (2), create (2), account (2), donate (2), menu (2), add, topic, cookie, statement, statistics, conduct, legal, safety, contacts, disclaimers, text, available, additional, may, apply, site, you, agree, registered, trademark, non, profit, organization, wikimedia, foundation, inc, creative, commons, attribution, sharealike, license, rendered, parsoid, last, edited, 2026, utc, hidden, categories, december, 2021, webarchive, template, category, retrieved, org, index, php, title, api_testing, oldid, 1364804887, soak, pair, orthogonal, array, manual, graphical, static, mutation, white, grey, scenario, based, fuzz, exploratory, pairs, style, symbolic, regression, negative, installation, dynamic, program, analysis, differential, destructive, conformance, concurrent, concolic, benchmark, techniques, tactics, book, gao, tao, jie, 2709, 1109, sose, 00015, doi, why, 2009, addison, wesley, professional, 978, 0321579362, isbn, 312, succeeding, cohn, mike, february, 2012, composite, app, speak, october, 2011, fight, scripts, eric, knipp, gary, olliffe, guidance, framework, designing, great, onus, enterprise, sean, kenefick, january, produce, better, layered, strategy, diego, giudice, april, wave, evaluation, fta, out, going, cameron, philipp, edmonds, stickyminds, interview, jonathan, cooper, march, protects, applications, reputations, visual, elements, work, friendly, which, communication, between, ethical, hacking, pentester, finds, integrations, due, incorrect, could, exploit, gaps, mimicking, hacker, accessing, disrupting, certain, conditions, ability, loads, simulates, real, world, workloads, goal, bottlenecks, maximum, number, users, load, transmits, invalid, unknown, fuzzer, generates, sequences, records, uncovered, fuzzing, actual, running, focuses, monitoring, resource, leaks, detected, breakdowns, confirms, matches, match, closely, aims, ensure, consistently, interact, systems, applies, interoperability, smallest, parts, called, units, proper, operation, where, interacts, knowing, internal, workings, provides, observes, generated, responds, validates, providing, verifying, mainly, concerned, source, preliminary, crucial, functions, identifies, major, before, further, improves, efficiency, accuracy, process, automatically, generate, analyze, through, learning, patterns, anomalies, there, several, some, increase, while, decreasing, reliance, vast, majority, efforts, much, possible, then, reserved, validating, typical, iterations, require, considerable, rework, keep, pace, change, easier, sufficiently, verify, paths, back, associated, multitier, architectures, stable, complexity, recognised, more, suitable, especially, than, cited, similar, length, tibco, rendezvous, smtp, rmi, mqtt, tcp, transports, protocols, protocol, buffers, csv, edi, swift, jms, http, payloads, xml, json, rest, whether, return, correct, format, broad, range, feasible, requests, react, properly, failures, extreme, deliver, responses, respond, securely, conjunction, isolate, expand, environment, access, simulating, accessible, attacks, acceptable, amount, time, isolation, exercised, during, produces, consumes, within, including, erps, uis, mainframes, databases, esbs, restful, since, lack, now, critical, automating, serve, primary, difficult, rust, python, perl, javascript, java, outlines, electrical, electronics, science, glossaries, swebok, pmbok, omg, itil, iec, 9001, ireb, cmmi, bodies, knowledge, uml, profiler, infrastructure, ide, builder, debugger, compiler, build, stand, sbe, ddd, cco, bdd, atdd, practices, experience, quality, assurance, project, documentation, configuration, supporting, disciplines, tsp, semat, safe, rup, rad, psp, msf, mde, lean, kanban, iid, fdd, dsdm, dad, asd, frameworks, methodologies, waterfall, spiral, prototyping, incremental, cleanroom, paradigms, models, maintenance, debugging, construction, processes, core, activities, series, programmable, free, encyclopedia, item, projects, printable, version, download, pdf, print, export, switch, legacy, parser, get, shortened, url, information, permanent, here, general, english, talk, suomi, top, personal, special, pages, recent, community, portal, help, contribute, current, events, navigation, jump, content,
Text of the page (random words):
api testing wikipedia jump to content main menu main menu move to sidebar hide navigation main page contents current events random article about wikipedia contact us contribute help learn to edit community portal recent changes upload file special pages search search appearance donate create account log in personal tools donate create account log in contents move to sidebar hide top 1 api testing overview 2 api testing gui testing and test automation 3 types of api testing 4 see also 5 references toggle the table of contents api testing 2 languages suomi 中文 edit links article talk english read edit view history tools tools move to sidebar hide actions read edit view history general what links here related changes upload file permanent link page information cite this page get shortened url switch to legacy parser print export download as pdf printable version in other projects wikidata item appearance move to sidebar hide from wikipedia the free encyclopedia automated software testing of programmable application interfaces apis part of a series on software development core activities data modeling processes requirements design construction engineering testing debugging deployment maintenance paradigms models agile cleanroom incremental prototyping spiral v model waterfall methodologies frameworks asd dad devops dsdm fdd iid kanban lean sd less mde msf psp rad rup safe scrum semat tdd tsp up xp supporting disciplines configuration management deployment management documentation project management quality assurance user experience practices atdd bdd cco cd ci ddd pp sbe stand up tdd xp tools build automation compiler debugger gui builder ide infrastructure as code profiler release automation uml modeling standards bodies of knowledge cmmi ieee standards ireb iso 9001 iso iec standards itil omg pmbok swebok glossaries artificial intelligence computer science electrical and electronics engineering outlines software development computer programming programming languages c c c java javascript perl python rust v t e api testing is a type of software testing that involves testing application programming interfaces apis directly and as part of integration testing to determine if they meet expectations for functionality reliability performance and security 1 since apis lack a gui api testing is performed at the message layer 2 api testing is now considered critical for automating testing because apis serve as the primary interface to application logic and because gui tests are difficult to maintain with the short release cycles and frequent changes commonly used with agile software development and devops 3 4 api testing overview edit api testing involves testing apis directly in isolation and as part of the end to end transactions exercised during integration testing 1 beyond restful apis these transactions include multiple types of endpoints such as web services esbs databases mainframes web uis and erps api testing is performed on apis that the development team produces as well as apis that the team consumes within their application including third party apis 5 api testing is used to determine whether apis return the correct response in the expected format for a broad range of feasible requests react properly to edge cases such as failures and unexpected extreme inputs deliver responses in an acceptable amount of time and respond securely to potential security attacks 1 4 service virtualization is used in conjunction with api testing to isolate the services under test as well as expand test environment access by simulating apis services that are not accessible for testing api testing commonly includes testing rest apis or soap web services with json or xml message payloads being sent over http https jms and mq 2 6 it can also include message formats such as swift fix edi and similar fixed length formats csv iso 8583 and protocol buffers being sent over transports protocols such as tcp ip iso 8583 mqtt fix rmi smtp tibco rendezvous and fix 7 8 api testing gui testing and test automation edit api testing is recognised as being more suitable for test automation and continuous testing especially the automation used with agile software development and devops than gui testing 3 4 reasons cited include system complexity gui tests can t sufficiently verify functional paths and back end apis services associated with multitier architectures apis are considered the most stable interface to the system under test short release cycles with fast feedback loops agile and devops teams working with short iterations and fast feedback loops find that gui tests require considerable rework to keep pace with frequent change tests at the api layer are less brittle and easier to maintain for these reasons it is recommended that teams increase their level of api testing while decreasing their reliance on gui testing api testing is recommended for the vast majority of test automation efforts and as much edge testing as possible gui testing is then reserved for validating typical use cases at the system level mobile testing and usability testing 3 4 9 types of api testing edit there are several types of tests that can be performed on apis some of these include smoke testing functional testing security testing penetration testing and validation testing artificial intelligence ai used in api testing improves the efficiency and accuracy of the testing process it can automatically generate test cases identify potential issues and analyze test results through machine learning to identify patterns and anomalies 10 smoke test this is a preliminary test that checks if the most crucial functions of an api are working correctly and identifies any major issues before further testing functional testing this type of testing validates a software system against its functional requirements by providing input and verifying the output it mainly involves black box testing and is not concerned with the source code black box testing this is a type of testing where the tester interacts with the api without knowing its internal workings the tester provides input and observes the output generated by the api to identify how it responds to expected and unexpected user actions unit testing this tests the smallest parts of an application called units for proper operation in api testing this includes testing single endpoints with a single request interoperability testing this test checks if an api can interact with other software components and systems without compatibility issues this applies to soap apis reliability testing this tests apis to determine if they meet expectations for functionality reliability performance and security it aims to ensure that the api consistently performs as expected validation testing this confirms the software matches business requirements and if api tests match expected results it is closely related to user acceptance testing runtime error detection this evaluates the actual running of an api and focuses on monitoring execution errors resource leaks and error detection detected errors are fixed to prevent runtime breakdowns fuzzing this test transmits random invalid or unexpected input to an api to find unknown bugs and defects an api fuzzer generates test inputs and request sequences to the api and records the response to see if any bugs or security vulnerabilities are uncovered load test this type of testing simulates real world workloads to see how a system or application performs the goal is to find bottlenecks and determine the maximum number of users or transactions the system can handle performance testing this type of testing evaluates how an api performs under certain conditions to assess the api s ability to handle high loads and maintain high performance levels security testing this checks for vulnerabilities in apis to find and fix security gaps it involves mimicking hacker actions to find bugs and prevent attackers from accessing or disrupting the api or its data penetration testing ethical hacking is used to assess the security of an api design an external pentester finds vulnerabilities in api integrations due to incorrect business logic or programming issues to identify security vulnerabilities that attackers could exploit web ui testing checks if the visual elements of a web application s user interface work correctly and are user friendly it is different from api testing which tests the communication between software components see also edit automated testing service virtualization software testing web api security references edit 1 2 3 testing apis protects applications and reputations by amy reichert searchsoftwarequality march 2015 1 2 all about api testing an interview with jonathan cooper by cameron philipp edmonds stickyminds august 19 2014 1 2 3 the forrester wave evaluation of functional test automation fta is out and it s all about going beyond gui testing archived 2015 05 28 at the wayback machine by diego lo giudice forrester april 23 2015 1 2 3 4 produce better software by using a layered testing strategy by sean kenefick gartner january 7 2014 onus for third party apis is on enterprise developers archived 2019 07 31 at the wayback machine by amy reichert searchsoftwarequality july 2014 a guidance framework for designing a great web api dead link by eric knipp and gary olliffe gartner august 20 2014 the fight against brittle scripts and software defects by adrian bridgwater dr dobb s journal october 26 2011 how do we learn composite app testing speak by adrian bridgwater dr dobb s journal february 14 2012 cohn mike 2009 succeeding with agile software development using scrum addison wesley professional p 312 isbn 978 0321579362 j gao c tao d jie ĺ s lu 2019 what is ai software testing and why ieee pp 27 2709 doi 10 1109 sose 2019 00015 cite book cs1 maint multiple names authors list link v t e software testing test levels acceptance testing system integration testing system testing integration testing unit testing test types techniques tactics a b testing benchmark compatibility testing concolic testing concurrent testing conformance testing continuous testing destructive testing development testing differential testing dynamic program analysis installation testing negative testing random testing regression testing security testing smoke testing software software performance testing stress testing symbolic execution test automation usability testing x box style black box testing all pairs testing exploratory testing fuzz testing model based testing scenario testing grey box testing white box testing api testing mutation testing static testing see also graphical user interface testing manual testing orthogonal array testing pair testing soak testing software reliability testing stress testing web testing retrieved from https en wikipedia org w index php title api_testing oldid 1364804887 category software testing hidden categories articles with short description short description is different from wikidata webarchive template wayback links all articles with dead external links articles with dead external links from december 2021 cs1 maint multiple names authors list this page was last edited on 18 july 2026 at 16 46 utc page was rendered with parsoid text is available under the creative commons attribution sharealike 4 0 license additional terms may apply by using this site you agree to the terms of use and privacy policy wikipedia is a registered trademark of the wikimedia foundation inc a non profit organization privacy policy about wikipedia disclaimers contact wikipedia legal safety contacts code of conduct developers statistics cookie statement mobile view search search toggle the table of contents api testing 2 languages add topic
|
