# #169722660 MMBC - Telkom speedy

https://www.pivotaltracker.com/story/show/169722660

## Test Scenario
### Transaction

Scenario Outline: Inquiry, Create and Get Detail Transaction Telkom Postpaid MMBC
    Given login for telkom postpaid MMBC as a partner <partner>
    When inquiry for telkom postpaid MMBC from transaction type <Transaction> by partner <partner> by input mock number <mock_number>, product id <product_id>, and status code <HTTP_RC_INQUIRY>
    Then inquiry for telkom postpaid MMBC has been requested with response code <rc_inquiry>
    When transaction for telkom postpaid MMBC from transaction type <Transaction> by partner <partner> by input mock number <mock_number>, product id <product_id>, and status code <HTTP_RC_TRANSACTION>
    Then transaction for telkom postpaid MMBC has been created with response code <rc_transaction>
    When get transaction detail for telkom postpaid MMBC from transaction type <Transaction> by partner <partner> with status code <HTTP_RC_GET_DETAIL>
    Then response code for telkom postpaid MMBC with <Transaction> from kraken <rc_get_detail_trx>

    Examples:
      |Transaction|partner|mock_number|product_id|HTTP_RC_INQUIRY|rc_inquiry|HTTP_RC_TRANSACTION|rc_transaction|HTTP_RC_GET_DETAIL|rc_get_detail_trx|
      |Purchase Success|MallOn_v2|0218900001|654|200|00|201|10|200|00|
      |Purchase Success 2 bill|MallOn_v2|0218800007|654|200|00|201|10|200|00|
      |Purchase Failed|MallOn_v2|0218700001|654|200|00|201|10|200|50|
      |Purchase Failed|MallOn_v2|0218800003|654|200|00|201|10|200|51|
      |Purchase Failed|MallOn_v2|0218800004|654|200|00|201|10|200|51|
      |Purchase Failed|MallOn_v2|0218800006|654|200|00|201|10|200|51|
      |Purchase Pending|MallOn_v2|0218800009|654|200|00|201|10|200|10|
      |Purchase Pending|MallOn_v2|081234000019|654|200|00|201|10|200|10|
      |Inquiry Failed|MallOn_v2|0218800008|654|200|26|200|51|0|0|
      |Inquiry Failed|MallOn_v2|0218800001|654|200|20|200|51|0|0|
      |Inquiry Failed|MallOn_v2|0218800005|654|200|50|200|51|0|0|
      |Purchase Advice Success|MallOn_v2|0218900002|654|200|00|201|10|200|00|
      |Purchase Advice Failed|MallOn_v2|081234000014|654|200|00|201|10|200|20|
      |Purchase Advice Failed|MallOn_v2|081234000020|654|200|00|201|10|200|10|
      
#### On SSH Log (Request Body)

On Inquiry
Scenario: Check "raw_data" on adapter.request 	
    Given User already success made the transaction
    When User grep SSH log on Terminal
    Then SSH log appeared
    And Get the parameter in "raw_data" is same with "Document for Inquiry Request"
    
On Payment
Scenario: Check "raw_data" on adapter.request 	
    Given User already success made the transaction
    When User grep SSH log on Terminal
    Then SSH log appeared
    And Get the parameter in "raw_data" is same with "Document for Payment Request"

Scenario: Check "paramrequest" on biller.purchase.request	
    Given User already success made the transaction
    When User grep SSH log on Terminal
    Then SSH log appeared
    And Get the value in every parameter on "paramrequest" is same with the value in every parameter on "raw_data" on adapter.request
    
Scenario: Check "requestmessage" on callback 	
    Given User already success made the transaction
    When User grep SSH log on Terminal
    Then SSH log appeared
    And Get the parameter in "requestmessage" is same with "Document for Response Get Transaction Detail"

#### On SSH Log (Response Body)

Scenario: Inquiry Success
    Given "Request inquiry body" already exist
    When User do inquiry
    Then Inquiry succeed
    And "response" on Inquiry SSH Log appeared
    And Get the value in every parameter on "Response body" has results that match with "Inquiry Response Parameter Mapping" on "Document" based on "response" on Inquiry SSH Log
    
Scenario: Payment Success
    Given "Request payment body" already exist
    When User do payment
    Then Payment succeed
    And "response" on Payment SSH Log appeared
    And Get the value in every parameter on "Response body" has results that match with "Payment Response Parameter Mapping" on "Document" based on "response" on Payment SSH Log

#### Manual Update

Scenario: Force to Failed
    Given User already success made the transaction
    And User already on transaction page on Sentinel
    When Search the transaction by transaction_id
    And User do manual update (Force to Failed) for the transaction
    Then "Force to Failed" succeed
    And The "Pending" transaction changed into "Failed"

Scenario: Force to Success
    Given User already success made the transaction
    And User already on transaction page on Sentinel
    When Search the transaction by transaction_id
    And User do manual update (Force to Success) for the transaction
    And Input "Ref Number" in the "Manual Update Form"
    Then "Force to Success" succeed
    And The "Failed" transaction changed into "Success"