Postman Testrunner Framework

From Vincents CV Wiki
Revision as of 09:18, 28 May 2019 by Vincent (talk | contribs) (Overview)

Jump to: navigation, search

Overview

The Postman Testrunner Framework was born out of a need to test our API serving our mobile banking apps, in a large pan-company integrated test environment, over which we had little control.
Our API server(s) (platform) acts as an aggregator of a number of different core online banking systems (OLB's), each serving many financial institutions (FI's), and each with its own API data/interface contract.
We needed a simple check of API functionality, capable of exercising all integration paths across the range of different OLB data interfaces, and FI/user configurations. To do this, it had to be flexible so that it could run for a range of users, FI's, and OLB's, as well as via different test instances of our platform.
Using network capturing tools (Fiddler, Burp Suite, MITM Proxy) we traced the API calls from mobile app and designed a Postman solution that emulates the app's sequence of API calls.
for a variety of users as they would have been made by the application. 

For a test user to be able to start using the application they need to select the test environment that has an instance of the platform, a code to select the FI, and the user's credentials (as well as selecting the type of device). Thereafter, the information required must be obtained in preceding calls. For example, if you want to test a transfer scenario, you need to first obtain a list of their accounts. The development teams had been using Postman for over a year and had built up a collection with 100+ endpoints and requests, many with test scripts that extracted data from the responses and saved them to the globals. The task, then, meant we needed to simply orchestrate the correct sequence of API requests to fulfillx the feature test scenarios. Finally, we need to handle different responses. We may receive different success or failure codes, but also we may receive information that makes the feature incapable of being executed, eg, if the feature is switched off for the FI, or a user isn't configured to permit it.

Objectives

Code Library

Postman Object Model

classes in Code lib

Settings & Variables

orthogonal syntax cascading over riding values

userActions

Testrun Datafiles

TFS

powershell script variables builds

- base
- Fi's
- time schedule

build agents

PTFWeb

Dashboards of results