The Swag of Performance Testing
Almudena Vivanco
(@MrsDaehin)
import random
import time
import requests
class Speaker(object):
def __init__(self):
born = "Avilés - Asturias"
studies = "Applied Maths and Computability"
jobdescription = "Performance Jedi"
company = "SCRM"
project = "LidlPlus"
talks = [VLC Testing, Devops BCN, DevopsDays, WebPerfDays, Velocity]
def talk(self):
start_timer = time.time()
r = requests.get('http://www.slideshare.net/almudenavivanco')
r.raw.read()
latency = time.time() - start_timer
self.custom_timers[ExpoQA] = latency
if __name__ == '__main__':
speech = Speaker()
speech.talk()
print trans.custom_timers
The OpenAPI Specification, formerly known
as Swagger Specification, is a simple yet
powerful way of describing RESTful APIs,
in a machine and human readable format,
using JSON or YAML. It has a large
ecosystem of tools that can help you
design, build, document, test, and visualize
your APIs.
A tool to describe your APIs following OpenAPI Specification
General Information
Host
BaseUrl
Tags
Protocol
Path
Methods
Model definition
Today’s problem with Microservices development
https://medium.com/cloudscaleqa/best-practices-for-shift-right-and-shift-left-testing-approaches-in-an-agile-environment-c95dcb1e621e
Easy Generation of Mocks from the API spec
Mock in Flask - Python
Client and model - Python
Jmeter Client
Description of Endpoints
Logical Aggrupation of
APIs
WorkLoad containing a
controller
Jmeter Client ReUsable
Swagger2Yaml
The sWag of performance Testing
The sWag of performance Testing
The sWag of performance Testing

The sWag of performance Testing

Editor's Notes

  • #4 To infinite and beyond! Open API is an Specification to help us desribing RESTFUL APIs in a human readable format using JSON or Yaml. We will be using Smartbear opensource tools in order to interact with the Documents and get the most profit out of it.
  • #8  Not all services can be described by the OpenAPI specification, and it was not intended to cover every possible case of RESTful APIs. BUT most of the restful API’s we use can be described with this language. And of course can be interpreted by everyone in a useful and easy way. That is the main goal of our job  So what shall we include in our specification? Operations: GET, POST, DELETE, PUT, PATCH … Api parameters: body or query parameters Authorization: bearer, hmac … Additional Info With this we generate interative Documentation : https://editor.swagger.io/
  • #11 What happens in real world. We have a lot of integrations and a lot of microservices calling one to another that we need to test.
  • #13 In my currnt Project we are migrating forma monolithic service to a microservices First thing was to créate a API Gateway where we are exposing the different services once we have migrated them.