QA Unit & Functional Test Writer - Long-Term Opportunity

== Fintech company seeks QA unit & functional test script writer ==

Must have experience with Stripe and knowledge of the legacy "charge" flow versus the modern "payment intents" and "payment method" object transaction flow. Must have working experience with postman and writing manual unit and functional tests with steps-to-reproduce and respective inputs

NOTE: If you do not have this experience, please do not apply as you'll be unable to satisfy the requirements and payment will not be rendered.

== Background ==

We've had a legacy XML API for credit card transactions using the traditional "charge" model similar to Stripe's legacy Charges API (just post the card data with the amount to charge). For example, 1 endpoint is called with a payload that contains a raw card number and an amount to be charged. We have a mature unit testing spreadsheet for it.

We now have a a RESTful API which has a different workflow more closely aligned with Stripe's PaymentIntents process. In this workflow, a PaymentIntent object is created (like an invoice) and then a second object is created for a PaymentMethod (ie. card number). Those 2 items are connected, the card is authorized via "Confirm", and then the transaction is charged via "Capture". This may be performed in 1 combined API call or as many as 5 API calls. As such, there are many permutations of workflows within those 5. This differs from the legacy method of posting all this data together in 1 request.

The RESTful API has a server-side NodeJS SDK which invokes the API.

We have a comprehensive unit testing spreadsheet for the server-side SDK along with a few RESTful endpoints but we do not have a comprehensive RESTful unit test list. Only a few tests have been included.

The goal of this project is to create 1 comprehensive and up-dated suite of unit and functional test scripts for the RESTful API and its server-side library: To do this:

(1) Do a gap analysis of the "Legacy" XML "charge/sale" API tests against the "New" RESTful "paymentIntents, paymentMethods, confirm/capture" API documentation (to be provided).
(1. a) Identify which tests from the Legacy list are accounted for by a parallel test in the New list.
(1.b) Identify which tests from the Legacy list do not have an equivalent in the New list and therefore must be written.

(2) Write the unit tests in the New list which accomplish filling the gaps from 1.b. All tests must include steps to reproduce, expected results, URLs, URL parameters, headers, GET queries, and all probable permutations of POST/PUT payloads.
(2.a) In the event of 1.a, if there is a close match which requires minor changes or additions to the input/body, either create a new test or revise the inputs/body of the matched test provided that it has no material impact on the existing test's outcome.
(2.b) Be sure to account for all probable permutations of each test flow. For example...
Scenario1.Test1: (A) create payment intent, (B) create payment method with given test data, (C) attach payment method to payment intent, (D) confirm payment intent, (E) capture payment intent.
Scenario1.Test2: (A) create payment intent with automatic confirmation, (B) create payment method with given test data, (C) attach payment method to payment intent, (D) capture payment intent (confirmation was already performed automatically per step 1)
Scenario1.Test3: (A) create payment method (b) Create payment intent with with automatic confirmation and automatic capture and payment method ID from step A
Scenario1.Test4: (A) Create payment intent with payment_method_data property containing raw PAN and with automatic confirmation and automatic capture.
Scenario1.Test5: (A) Create payment intent with payment_method_data property containing raw PAN and with manual confirmation and manual capture, (B) confirm payment intent, (c) capture ....
etc etc etc

(3) Populate all API unit tests in a Postman collection and export it. Verify all your tests are accurate

You will be given a spreadsheet containing lists of both the RESTful and legacy tests with API documentation on each row, test inputs on each row, codepens, API secrets, test card numbers, and a postman collection for the new RESTful API.