Staff
470
edits
Changes
→Overview
:To initiate a check, we select a platform instance, a code for the FI, a useragent for the device, and then enter the user's credentials. Thereafter, the information required for subsequent scenarios must be obtained in prior calls. For example, to test a transfer scenario, you need to first obtain a list of their accounts.
:Our development teams have been using Postman for over a year and built up a collection with 100+ endpoints and requests. Many requests are furnished with helpful test scripts that extract data from the response, and saves them to the Postman global/environment variables. The collection is an organised into feature folders, and alphabetised to facilitate interactive functional testing of the platform API. However, the developer/test analyst must know the sequence of calls to make to start a session, and then they can perform some feature testing.
:This collection is actively maintained and versioned with pull requests and reviews in a Git repo. It is a really wonderful resource , and this project tries to leverage it's value by trying to implementing a framework that can orchestrate the correct sequence of API requests to automate some common functional (API) scenarios.fulfillx :The Postman Testrunner Framework (PTF) uses an external data file to specify a sequence of steps called userActions. A userAction executes a request from the feature test scenariosunderlying collection, and then has a list of handlers for the possible response codes. Response handlers are little snippets of code that determine the next userAction to perform. FinallyWhen no next userAction is specified in the response handler, we need execution moves to handle different responsesthe next userAction in the external data file until the scenario is completed. The PTF is a simple state-machine. We may receive :The PTF implements a data store of the information necessary to be able to test with many different success or failure codesusers, FI's, OLB's, deploy instances, but also we may receive information etc. A data syntax was developed that makes the feature incapable of being executedlinks different data types, eg, if and selects the feature is switched off values necessary to initiate a scenario for a user. The input variables are processed, the FIrelevant data links expanded, or a user isn't configured so that the Postman global and environment variables are ready prior to permit itthe first request.:Throughout the implementationA custom reporter was developed to receive the
==Objectives==
