Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Because every QA should know API Testing

Because every QA should know API Testing

Frederico Moreira

May 07, 2019
Tweet

More Decks by Frederico Moreira

Other Decks in Technology

Transcript

  1. Brazil (Minas Gerais) • Café, testes e pão de queijo

    • MTC - Minas Testing Conference Agile Testers • Fórum • Agile Testers Conference UAI, TREM, SÔ, PÃO DE QUEIJO • if(cachaça || bagaço) @fredaomoreira @farfetch
  2. @ramilomcneves @farfetch Brazil (Petrópolis - Rio de Janeiro) • Tester

    Automation Engineer • In love with football –Flamengo (Brazil) –Porto (Portugal) • Living two years in Porto • Second time speaking at PTM
  3. API • Who is here doing an API test today?

    • Who has tested the API? • Who automates API testing?
  4. What is an API? “An API is created when a

    software company intends that other software developers develop products associated with its service.”
  5. Examples • Google ◦ Google Maps ◦ Google Flights •

    Accommodation ◦ Trivago ◦ Airbnb • Payment providers ◦ Paypal ◦ Klarna
  6. Service Level Tests Subcutaneous Test - Martin Fowler Fills gap

    between unit and UI tests They occur in parallel to the development Focus on functionality rather than behavior / experience
  7. The most common to find in the market are new

    designs using Rest, over HTTP protocol. But you can use Rest with other protocols like TCP, UDP and gRPC (http:/ /www.grpc.io/).
  8. What we validate in a api test? ➔ http status

    code 200, 201, 400, 401, 500 ... ➔ body content Json, Plain text, XML ... ➔ http headers "Content-Type"":"application/json"