TC_E_30_CSMS — Check Transaction status - Transaction with id ongoing - without message in queue
TC_E_30_CSMS — Check Transaction status - Transaction with id ongoing - without message in queue
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block E. Transactions, page 401.
Identification
| Field | Value |
|---|---|
| Test case name | Check Transaction status - Transaction with id ongoing - without message in queue |
| Test case Id | TC_E_30_CSMS |
| Use case Id(s) | E14 |
| Requirement(s) | E14.FR.02,E14.FR.05 |
| System under test | CSMS |
| Functional block | E. Transactions |
Description
The CSMS is able to request the status of a transaction and to find out whether there are queued transaction-related messages, using the GetTransactionStatusRequest message.
Purpose
To verify if the CSMS is able to request the status of queued TransactionEventRequest messages from a specific transaction by sending a GetTransactionStatusRequest with a transactionId. The OCTT will respond that there is NO message queued belonging to the ongoing transaction with the requested id.
Prerequisite(s)
N/a
Before (Preparations)
Configuration State:
- N/a
Memory State:
- N/a
Reusable State(s):
- State is EnergyTransferStarted
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The OCTT responds with a GetTransactionStatusResponse With ongoingIndicator is true messagesInQueue is false | 1. The CSMS sends a GetTransactionStatusRequest |
Tool validations
Step 1:
Message: GetTransactionStatusRequest
- transactionId must be <Generated transactionId from Before>
Post scenario validations
- N/a