> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/psdk-latest/reference-material/self-assessment/assessment-test-cases.md). # Assessment Test Cases {% columns %} {% column width="25%" %}
{% endcolumn %} {% column width="25%" %} {% endcolumn %} {% column width="16.66666666666666%" %} **Version:**\ **Date:** {% endcolumn %} {% column width="33.333333333333336%" %} v2.0.9\ 7th October 2022 {% endcolumn %} {% endcolumns %} *** ## Mandatory Test Cases ### Device
Test 1.01 – About/Help Screen
Test 1.01 – About/Help Screen
Objective:Check if the POS application can obtain the payment application details and provide the information to the operator for helpdesk/service request from field.
Test:

Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Perform Login with Payment Application.
  3. Navigate to About/Help Screen.

About/Help screen should have PSDK, payment application information, serial number of the device and other relevant information required for trouble shooting. Provide screenshot.

Test 1.02 – Login Failure
Test 1.01 – About/Help Screen
Objective:Check if the POS application is handling login failures gracefully and establish a login successfully after recovery from failure.
Test:

Please provide individual log file for the entire sequence identified with test case number.

  1. Change settings of Payment Application to simulate login failure in payment app (see regional instruction or contact Verifone for instructions).
  2. Launch POS application.
  3. Perform Login operation.
  4. If there is no UI button for Login, the POS application must show an error to the user informing them to contact helpdesk/support if reboot does not recover the device.
  5. If there is an option to Login, the POS application must inform the user that Login failed and help desk must be contacted if problem persists even after reboot. Provide screenshot.
  6. Provide logs for above steps.
  7. Revert settings of Payment Application get success Login.
  8. Perform Login operation, it shall complete successfully.
  9. Close POS application.
Test 1.03 – Transaction Abort (Only for Off device integration)
Test 1.01 – About/Help Screen
Objective:Ccheck if the POS application allows the POS operator to cancel a transaction.
Test:

Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Start sale transaction with any amount
  3. Cancel the transaction from POS when terminal shows present card screen.
  4. Wait for transaction response.
  5. Close POS application.
### Payment
Test 2.01 - Successful Sale/Purchase Transaction
Test 1.01 – About/Help Screen
Objective:Ensure the PSDK API’s are called in correct sequence.
Test:

Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Perform Sale transaction with any amount and a valid card, the transaction must be approved.
  3. Close POS application.
Test 2.02 - Successful Sale/Purchase Transaction – Sequential
Test 1.01 – About/Help Screen
Objective:Ensure the PSDK API’s are called in correct sequence.
Test:

Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Perform 1st Sale transaction with any amount and a valid card, the transaction must be approved.
  3. Perform 2nd Sale transaction with any amount and a valid card, the transaction must be approved.
  4. Close POS application.
Test 2.03 - Declined Sale/Purchase Transaction
Test 1.01 – About/Help Screen
Objective:Ensure declined cases are handled properly by POS
Test:

Please provide individual log file for the entire sequence identified with test Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Start a Sale transaction with any amount and a valid card.
  3. After card is presented, terminate the transaction before completion (early card removal or user cancel).
  4. Complete the transaction flow.
  5. Close POS application.
Test 2.04 - POS Recovery During Sale Transaction
Test 1.01 – About/Help Screen
Objective:

Check if the POS application can obtain the transaction details if it was stopped mid-way and re launched after transaction was completed.

Mandatory for Off device integration.

Mandatory for On device only if POS maintains a transaction history / last transaction view which operator can see from POS.

Test:

Please provide individual log file for the entire sequence identified with test Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Start a Sale transaction with any amount and a valid card.
  3. After card is presented, terminate the transaction before completion (early card removal or user cancel).
  4. Complete the transaction flow.
  5. Close POS application.
Test 2.03 - Declined Sale/Purchase Transaction
Test 1.01 – About/Help Screen
Objective:Ensure declined cases are handled properly by POS
Test:

Please provide individual log file for the entire sequence identified with test Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Start a Sale transaction with any amount and a valid card.
  3. After card is presented, terminate the transaction before completion (early card removal or user cancel).
  4. Complete the transaction flow.
  5. Close POS application.
Test 2.03 - Declined Sale/Purchase Transaction
Test 1.01 – About/Help Screen
Objective:Ensure declined cases are handled properly by POS
Test:

Please provide individual log file for the entire sequence identified with test Please provide individual log file for the entire sequence identified with test case number.

  1. Launch POS application.
  2. Start a Sale transaction with any amount and a valid card.
  3. After card is presented, terminate the transaction before completion (early card removal or user cancel).
  4. Complete the transaction flow.
  5. Close POS application.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.verifone.com/psdk-latest/reference-material/self-assessment/assessment-test-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.