MPESA API Test Cases
MPESA API Test Cases
MPESA API Test Cases
Send the request with an valid To test whether the request will go through
Functionality tests command id with a valid command id
Send the request with an invalid To test whether the request will go through
Functionality tests command id with an invalid command id
Send the request with a valid To test whether the request will be allowed
Functionality tests amount between 1-70000 on Mpesa with a valid amount
Send remarks with less then 200 To test whether less then 200 characters will
Functionality Tests characters be accepted in remarks
Send remarks with more then 200 To test whether more then 200 characters
Functionality Tests characters will be accepted in remarks
Send result url without an ip and To test whether the request will be accepted
Functionality tests port without an ip and port
Send queuetimeout URL with an ip To test whether the request will be accepted
Functionality tests and port with an ip and port
Send queuetimeout URL without an To test whether the request will be accepted
Functionality tests ip and port without an ip and port
Expected Results Actual Results
Authentication is
successful
Authentication is
unsuccessful
Authentication is
successful
1) Request is sent to
Authentication
API gateway is
unsuccessful A valid
successfully.
1) Requestis isreturned
response sent to to
API Gateway
the Partner.
Portal displays
successfully. https
2) Transfer ofAfunds
and transaction
valid
is isto
response
successful is returned
from any
successful
the Partner. MSISDN
organization
1) Request is to sent to
2) Transfer of funds
3) Valid
API result is
Gateway
from B2C business
returned withA valid
successfully.
account to Customer's
appropriate
response error to
is returned
MPESA account is
the Partner.
unsuccessful
1)
2) Request is sent to
3) Transfer
APIValid of funds
result
Gateway is
from B2C business
returned withA valid
successfully.
account to Customer's
appropriate
response error to
is returned
MPESA account is
the Partner.
unsuccessful
1)
2) Request is sent to
3) Transfer
APIValid of funds
result
gateway is
from B2C with
returned business
successfully. A valid
account to Customer's
appropriate
response is error to
returned
MPESA account is
the Partner.
unsuccessful
2) Transfer of funds
3) Valid result is
from B2C business
returned with
account to Customer's
appropriate error
MPESA account is
unsuccessful
3) Valid result is
returned with
appropriate error
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an
appropriate error
thrown: Invalid
CommandID
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an
appropriate error
thrown: Invalid Amount
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid Party B
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid Remarks
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid
ResultURL
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid
QueuetimeoutURL
Testing API Gateway- API Gateway integ
Authentication
Authentication Authentication
OUTPUT:
The user isappropriate error
able to view the message in the
testing page for C2B
To verify that the user can access APIs format {
Simulate Transaction
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Error
OUTPUT: appropriate error message in the
Message - "
To verify that the user must provide valid inputs format
} {
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Error
OUTPUT:
Message -appropriate
error message in the
"
format {
To verify that the user must provide valid inputs }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT:
Commandappropriate
error message in the
To verify that the user must provide a valid ID- "
format {
commandID }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT:
Amount - appropriate
error message in the
To verify that the user must provide a valid "
format {
Amount }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT:
To verify that the user must provide a valid MSISDN" appropriate error message in the
format {
msisdn }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT:
BillRefNo appropriate
error message in the
To verify that the user must provide a valid -"
format {
BillRefNo }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
To verify that the user must provide a valid Shortcode"
ShortCode }
OUTPUT: appropriate acknowledgement of
success message with "ConversationID",
To verify that the user must provide a valid "OriginatorConversationID",
commandID "ResponseDescription".
OUTPUT: appropriate error message in the
format {
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT: appropriate error message in the
To verify that the user must provide a valid CommandID - "
format {
commandID }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT: appropriate error message in the
To verify that the user must provide a valid Amount - "
format {
Amount }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT: appropriate error message in the
To verify that the user must provide a valid Amount - "
format {
Amount }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
To verify that the user must provide a valid OUTPUT:
Amount- "appropriate error message in the
format {
Amount }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
To verify that the user must provide a valid OUTPUT:
MSISDN - appropriate
" error message in the
MSISDN format
} {
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT: appropriate error message in the
To verify that the user must provide a valid MSISDN- "
MSISDN format
} {
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT:
MSISDN - appropriate
error message in the
To verify that the user must provide a valid "
format {
MSISDN }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT: appropriate error message in the
To verify that the user must provide a valid BillRefNumber -"
format {
BillRefNumber }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
OUTPUT: appropriate error message in the
To verify that the user must provide a valid BillRefNumber"
format {
BillRefNumber }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
To verify that the user must provide a valid BillRefNumber - "
OUTPUT: appropriate error message in the
BillRefNumber }
format {
"requestId": "",
"errorCode": "",
OUTPUT: appropriate error- Shortcode
message in-"the
To verify that the user must provide a valid "errorMessage": "Invalid
format {
shortCode }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
To verify that the user must provide a valid OUTPUT:
Shortcodeappropriate
-" error message in the
format {
shortCode }
"requestId": "",
"errorCode": "",
"errorMessage": "Error Occurred - Invalid
To verify that the user must provide a valid Shortcode - "
shortCode }
OUTPUT: appropriate acknowledgement of
success message with "ConversationID",
To verify that the user must provide a valid "OriginatorConversationID",
amount between 1-70,000 "ResponseDescription".
OUTPUT: appropriate acknowledgement of
success message with "ConversationID",
To verify that the user must provide a valid "OriginatorConversationID",
MSISDN "ResponseDescription".
OUTPUT: appropriate acknowledgement of
success message with "ConversationID",
To verify that the user must provide a valid "OriginatorConversationID",
MSISDN "ResponseDescription".
OUTPUT: appropriate acknowledgement of
success message with "ConversationID",
To verify that the user must provide a valid "OriginatorConversationID",
BillRefNo "ResponseDescription".
OUTPUT: appropriate acknowledgement of
success message with "ConversationID",
To verify that the user must provide a valid "OriginatorConversationID",
Shortcode "ResponseDescription".
Testing API Gateway- Core API integra
To test whether the request will go through with The request shall not go through with an
an invalid command id appropriate error thrown: Invalid CommandID
To test whether the request will be allowed on You should get an appropriate success message:
Mpesa with a valid amount The service has been accepted successfully
To test whether the request will be allowed on The request shall not go through with an
Mpesa with a negetive amount appropriate error thrown: Invalid Amount
To test whether an MSISDN of 12 numbers will be You should get an appropriate success message:
accepted The service has been accepted successfully
To test whether an MSISDN of 12 or more The request shall not go through with an in
numbers will be accepted appropriate error thrown:Invalid Party B
To test whether less then 200 characters will be You should get an appropriate success message:
accepted in remarks The service has been accepted successfully
To test whether more then 200 characters will be The request shall not go through with an in
accepted in remarks appropriate error thrown:Invalid Remarks
To test whether the request will be accepted with You should get an appropriate success message:
a valid ip and port The service has been accepted successfully
To test whether the request will be accepted The request shall not go through with an in
without an ip and port appropriate error thrown:Invalid ResultURL
To test whether the request will be accepted with The request shall not go through with an in
an ip and port appropriate error thrown:Invalid ResultURL
To test whether the request will be accepted The request shall not go through with an in
without an ip and port appropriate error thrown:Invalid ResultURL
Testing gateway- Core API integration
Subject Test case Objective
Send the request with an invalid To test whether the request will be allowed
Functionality tests identifier e.g. 6 on Mpesa with an invalid identifier
Send remarks with less then 200 To test whether less then 200 characters will
Functionality Tests characters be accepted in remarks
Send remarks with more then 200 To test whether more then 200 characters
Functionality Tests characters will be accepted in remarks
Send result url without an ip and To test whether the request will be accepted
Functionality tests port without an ip and port
Send queuetimeout URL with an ip To test whether the request will be accepted
Functionality tests and port with an ip and port
Send queuetimeout URL without an To test whether the request will be accepted
Functionality tests ip and port without an ip and port
Expected Results Actual Results
Authentication is
successful
Authentication is
unsuccessful
Authentication is
successful
Authentication is
unsuccessful
1) Request is sent to
API gateway
Portal displays https
successfully. A valid
and transaction is
response
successfulis returned to
the Partner.
1) Request is sent to
2) Valid result is
API Gateway
returned with
successfully. A valid
appropriate error
response is returned to
the Partner.
1)
2) Request
is sent
Valid result is to
API Gateway
returned with
successfully. A valid
appropriate error
response is returned to
the Partner.
1)
2) Request is sent
Valid result is to
API gateway
returned with
successfully. A valid
appropriate error
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an
appropriate error
thrown: Invalid
CommandID
The request shall not go
through with an
appropriate error
thrown: Invalid
identifier
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid Remarks
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid
ResultURL
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid
QueuetimeoutURL
Testing gateway- Core API integration
Subject Test case Objective
Send remarks with more then 200 To test whether more then 200 characters
Functionality Tests characters will be accepted in remarks
Send result url without an ip and To test whether the request will be accepted
Functionality tests port without an ip and port
Send queuetimeout URL with an ip To test whether the request will be accepted
Functionality tests and port with an ip and port
Send queuetimeout URL without an To test whether the request will be accepted
Functionality tests ip and port without an ip and port
Send the Occasion with less than To test whether Occasion will be accepted
Functionality tests 200 characters with less than 200 characters
Send Occasion with more then 200 To test whether occasion will go through with
Functionality tests characters more then 200 characters
Send the amount with a different To test whether the transaction will be
amount that was sent during c2b reversed with an amount not matching the
Functionality tests with a valid transaction ID intial C2B request
To test whether the transaction will be
Send an invalid transaction ID that reversed with a transaction ID not matching
Functionality tests does not exist the intial C2B request
Send the TransactionID with a valid To test whether a valid transaction can be
Functionality tests Transaction ID and valid shortcode queried
Expected Results Actual Results
Authentication is
successful
Authentication is
unsuccessful
Authentication is
successful
Authentication is
unsuccessful
1) Request is sent to
API gateway
Portal displays https
successfully. A valid
and transaction is
response
successfulis returned to
the Partner.
1) Request is sent to
2) Valid result is
API Gateway
returned and
successfully. A valid
transaction is reversed
response is returned to
the Partner.
1)
2) Request
is sent
Valid result is to
API Gateway
returned with
successfully. A valid
appropriate error
response is returned to
the Partner.
1)
2) Request is sent
Valid result is to
API gateway
returned with
successfully. A valid
appropriate error
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an
appropriate error
thrown: Invalid
CommandID
The request shall not go
through with an
appropriate error
thrown: Invalid
identifier
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid Remarks
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid
ResultURL
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid
QueuetimeoutURL
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
Send the request with a valid To test whether the request will go through
command id i.e with a valid command id through the API
Functionality tests TransactionStatusQuery gateway
Send the request with an invalid To test whether the request will be allowed
Functionality tests identifier e.g. 6 on Mpesa with an invalid identifier
Send the Party A with a MSISDN of To test whether a MSISDN of 10 digits will be
Functionality Tests 10 digits accepted
Send the Party A with a MSISDN of To test whether a MSISDN of more or less
Functionality Tests more then 10 digits then 10 digits will be accepted
Send remarks with less then 200 To test whether less then 200 characters will
Functionality Tests characters be accepted in remarks
Send remarks with more then 200 To test whether more then 200 characters
Functionality Tests characters will be accepted in remarks
Send result url without an ip and To test whether the request will be accepted
Functionality tests port without an ip and port
Send queuetimeout URL with an ip To test whether the request will be accepted
Functionality tests and port with an ip and port
Send queuetimeout URL without an To test whether the request will be accepted
Functionality tests ip and port without an ip and port
Send the amount with an invalid To test whether a transaction that does not
Functionality tests transaction ID that does not exist exist can be queried
Send the Occasion with less than To test whether Occasion will be accepted
Functionality tests 200 characters with less than 200 characters
Send Occasion with more then 200 To test whether occasion will go through with
Functionality tests characters more then 200 characters
Expected Results Actual Results
Authentication is
successful Authentication is successful
Authentication is
unsuccessful Authentication is unsuccessful
Authentication is
successful Authentication is successful
Authentication is
unsuccessful
1) Request is sent to Authentication is unsuccessful
API gateway
successfully. A valid
Portal displays https
response is returned to
and transaction is
the Partner.
successful Portal displays https and transaction is successful
2) Valid result is 1) Request is sent to API gateway successfully. A
1) Request is sent to
returned with success valid response is returned to the Partner.
API Gateway
message and 2) Valid result is returned with success message
successfully. A valid
transaction details and transaction details
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API Gateway successfully. A
1) Request is sent to
returned with valid response is returned to the Partner.
API Gatewayerror
appropriate 2) Valid result is returned with appropriate error
successfully. A valid
response is returned to
1)
theRequest
Partner.is sent to
API gateway
2) Valid result is 1) Request is sent to API Gateway successfully. A
successfully. A valid
returned with valid response is returned to the Partner.
response is returned
appropriate error to 2) Valid result is returned with appropriate error
the Partner.
2) Valid result is 1) Request is sent to API gateway successfully. A
returned with valid response is returned to the Partner.
appropriate error 2) Valid result is returned with appropriate error
You should get an
appropriate success
message: The service
has been accepted An appropriate success message is displayed: The
successfully service has been accepted successfully
The request shall not go
through with an
appropriate error
thrown: Invalid The request does not go through with an
CommandID appropriate error thrown: Invalid CommandID
The request shall not go
through with an
appropriate error
thrown: Invalid The request does not go through with an
identifier appropriate error thrown: Invalid identifier
You should get an
appropriate success
message: The service
has been accepted An appropriate success message is displayed: The
successfully service has been accepted successfully
The request shall not go
through with an in
appropriate error The request does not go through with an in
thrown:Invalid Party A appropriate error thrown:Invalid Party A
You should get an
appropriate success
message: The service
has been accepted An appropriate success message is displayed: The
successfully service has been accepted successfully
The request shall not go
through with an in
appropriate error The request does not go through with an in
thrown:Invalid Remarks appropriate error thrown:Invalid Remarks
You should get an
appropriate success
message: The service
has been accepted An appropriate success message is displayed: The
successfully service has been accepted successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid The request does not go through with an in
ResultURL appropriate error thrown:Invalid ResultURL
You should get an
appropriate success
message: The service
has been accepted An appropriate success message is displayed: The
successfully service has been accepted successfully
The request shall not go
through with an in
appropriate error The request does not go through with an in
thrown:Invalid appropriate error thrown:Invalid
QueuetimeoutURL QueuetimeoutURL
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API Gateway successfully. A
returned with valid response is returned.
appropriate error 2) Valid result is returned with appropriate error
Send call back url without an ip and To test whether the request will be accepted
Functionality tests port without an ip and port
Send the TransactionDesc with less To test whether TransactionDesc will be
Functionality tests than 200 characters accepted with less than 200 characters
On the phone when the STK menu To test whether the transaction will complete
Functionality tests pops up enter a valid Mpesa PIN successfully with a valid Mpesa PIN
Authentication is
successful Authentication is successful
Authentication is
unsuccessful Authentication is unsuccessful
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API Gateway successfully. A
returned with valid response is returned.
appropriate error 2) Valid result is returned with appropriate error
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API Gateway successfully. A
returned with valid response is returned.
appropriate error 2) Valid result is returned with appropriate error
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API Gateway successfully. A
returned with valid response is returned.
appropriate error 2) Valid result is returned with appropriate error
1) Request is sent to
API gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API gateway successfully. A
returned with valid response is returned.
appropriate error 2) Valid result is returned with appropriate error
1) Request is sent to
API gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API gateway successfully. A
returned with valid response is returned.
appropriate
1) Request iserror
sent to 2) Valid result is returned with appropriate error
API gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is 1) Request is sent to API gateway successfully. A
returned with valid response is returned.
appropriate error 2) Valid result is returned with appropriate error
You should get an
appropriate success
message: The service
has been accepted An appropriate success message: The service has
successfully been accepted successfully
You should get an
appropriate success
message: The service
has been accepted An appropriate success message: The service has
successfully been accepted successfully
The request shall not go
through with an in
appropriate error The request does not go through with an in
thrown:Invalid Remarks appropriate error thrown:Invalid Remarks
You should get an
appropriate success
message: The service
has been accepted An appropriate success message: The service has
successfully been accepted successfully
The request shall not go
through with an in
appropriate error
thrown:Invalid The request does not go through with an in
ResultURL appropriate error thrown:Invalid ResultURL
The request shall not go
through with an in
appropriate success
message: The service The request does not go through with an in
has been accepted appropriate success message: The service has
successfully been accepted successfully
Send an invalid STK push query STK query for paybill account with invalid
request to gateway - Paybill account shortcode is unsuccessful. Request is
has wrong shortcode but correct processed by the API gateway and
password, correct appropriate error message is retuned in the
Functionality tests CheckoutRequestID and timestamp result
Send an invalid STK push query STK query for paybill account with invalid
request to gateway - Paybill account password is unsuccessful. Request is
has wrong password but correct processed by the API gateway and
shortcode, correct appropriate error message is retuned in the
Functionality tests CheckoutRequestID and timestamp result
Send an invalid STK push query STK query for paybill account with invalid
request to gateway - Paybill account timestamp is unsuccessful. Request is
has wrong timestamp but correct processed by the API gateway and
shortcode, correct appropriate error message is retuned in the
Functionality tests CheckoutRequestID and password result
Send an invalid STK push query STK query for paybill account with invalid
request to gateway - Paybill account timestamp is unsuccessful. Request is
has wrong timestamp but correct processed by the API gateway and
shortcode, correct appropriate error message is retuned in the
Functionality tests CheckoutRequestID and password result
Send an invalid STK push query STK from paybill account with invalid
request to gateway - Paybill account CheckoutRequestID is unsuccessful. Request
has wrong CheckoutRequestID but is processed by the API gateway and
correct shortcode, correct appropriate error message is retuned in the
Functionality tests CheckoutRequestID and password result
Expected Results Actual Results
Authentication is
successful Authentication is successful
Authentication is
unsuccessful Authentication is unsuccessful
Portal is unable to
query and throws the
appropriate error Portal is unable to query and throws the
message appropriate error message
Portal is unable to
query and throws the
appropriate error Portal is unable to query and throws the
message appropriate error message
Portal is unable to
query and throws the
appropriate error Portal is unable to query and throws the
message appropriate error message
Portal is unable to
query and throws the
appropriate error Portal is unable to query and throws the
message appropriate error message
Portal is unable to
query and throws the
appropriate error Portal is unable to query and throws the
message appropriate error message
Portal is unable to
query and throws the
appropriate error Portal is unable to query and throws the
message appropriate error message
Testing gateway- Core API integration
Subject Test case Objective
Send request with transaction type Check Identity for paybill account with invalid
Check Identity with command ID password is unsuccessful. Request is
"CheckIdentity" to gateway - Paybill processed by the API gateway and
account has wrong password but appropriate error message is retuned in the
Functionality tests correct shortcode and timestamp result
Send request with transaction type Check Identity for paybill account with invalid
Check Identity with command ID password is unsuccessful. Request is
"CheckIdentity" to gateway - Paybill processed by the API gateway and
account has wrong timestamp but appropriate error message is retuned in the
Functionality tests correct shortcode and password result
Send request with transaction type Check Identity from paybill account with
Check Identity with command ID invalid phone number is unsuccessful.
"CheckIdentity" to gateway - with Request is processed by the API gateway and
an invalid phone number i.e less appropriate error message is retuned in the
Functionality tests than or more then 10 digits result
Send call back url without an ip and To test whether the request will be accepted
Functionality tests port without an ip and port
Authentication is
successful
Authentication is
unsuccessful
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
1) Request is sent to
API Gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
1) Request is sent to
API gateway
successfully. A valid
response is returned to
the Partner.
2) Valid result is
returned with
appropriate error
You should get an
appropriate success
message: The service
has been accepted
successfully
The request shall not go
through with an
appropriate error
thrown: Invalid
CommandID
Send the request with a credit score To test whether the correct credit score type
Functionality tests type as: Consumer will go through
Send the request with a credit score To test whether an invalid credit score type
Functionality Tests type as: Merchant will go through
Send the request with a credit score To test whether an invalid credit score type
Functionality Tests type as: Example will go through
Expected Results Actual Results
Authentication is
successful
Authentication is
unsuccessful
Authentication is
successful
Authentication is
unsuccessful
Send an invalid ProviderID but valid To test whether an invalid response will be
Functionality tests ProviderPassword and MSISDN returned using an Invalid ProviderID
Send an invalid MSISDN but valid To test whether an invalid response will be
Functionality tests ProviderPassword and ProviderID returned using an invalid MSISDN
Expected Results Actual Results
Authentication is
successful
Authentication is
unsuccessful
Authentication is
successful
Authentication is
unsuccessful