Scenario |
Scenario Description |
Req. Description |
SDS Section |
1 |
Verify that the GetAccountRateOfReturn operation is available in the VM Balances V5 web service and that it returns PRR data for a valid participant |
The Ventura Modernization Balances V5 web service will be modified to add a new operation called GetAccountRateOfReturn.
The GetAccountRateOfReturn operation will require that a participant SSN be passed in the request and will support the passing of an optional account list (AccountIds) along with three other optional data elements: PlanSponsorId, FromDate and ToDate to retuen PRR Data |
8.2,8.2.1 |
2 |
Verify whether the VM Balances V5 web service GetAccountRateOfReturn operation doesn't return any data back along with the calculated PRR for an invalid Participant SSN |
3 |
Ensure that a soapfault is not returned in the response for the GetAccountRateOfReturn operation when valid data is passed in the request |
If FromDate and ToDate are not passed in the request, ODS would not consider this to be a custom date range request and valid data will be passed as request. |
8.2.1 |
4 |
Ensure that a soapfault is returned in the response for the GetAccountRateOfReturn operation when invalid data is passed in the request
DL: I think you may be trying to capture the scenario where a non-null value is passed in the request for the date elements which would tie back to section 8.2.1 - this would be different than what is described in section 8.3 and would also need to be covered as a scenario |
If the ODS stored procedure is not available, the Ventura Modernization Balances V5 web service will return a soapfault to the channel and will not attempt to call the FPRS IOM to obtain the information |
8.3 |
5 |
Verify and compare whether the values received as response for a valid participant SSN is same as the data returned by the ODS stored procedure |
The GetAccountRateOfReturn operation will call a new ODS stored procedure to obtain the Personal Rate of Return (PRR) information, instead of calling the FPRS IOM that is used by the Ventura Modernization Transaction History V3 web service. In case if you don't get a response from the new operation, you will neither get a response from the ODS stotred procedure. |
8.3 |
6 |
Verify and compare whether you do not do not get a response from the new operation for an invalid participant SSN requested as you don’t get a response from the ODS Stored Procedure |
7 |
Verify whether for Get Investments operation in VM Balance V5 web service, we get the relevant PRR data for the valid participant SSN
DL: This would be part of a scenario that tests that the data returned by the new operation is in agreement with the old operation and not a separate scenario |
The GetInvestments operation will return PRR data for valid partcipant SSN and will not return any data for invalid participant SSN |
3 |
8 |
Verify and compare whether for Get Investments operation , the value which we get as response from the FPRS IOM is same as that of value which we get from the ODS Procedure for the GetAccountRateofReturn Operation for valid inputs.
DL: I'm not sure that you need to mention the IOM and the stored procedure here (except for informational purposes) since you are really testing the two operations - you would also want to make sure that you test the negative scenarios where you do not get a value from the old operation to ensure that there is also no value returned by the new operation |
9 |
Ensure that the VM Transaction History V4 web service will not return PRR data for valid Participant SSN and Account ID requested
DL: You also need to ensure that the ReturnPRR request parameter is no longer a valid parameter for the GetSummary operation |
A new version (V4) of the Ventura Modernization Transaction History web service will be created that will no longer provide Personal Rate of Return (PRR) information when a call is made to the GetSummary operation. The ReturnPRR request parameter is being removed so that Personal Rate of Return (PRR) can no longer be requested by the GetSummary operation. Therefore, the optional GetSummaryResponse\PlanSponsors\PlanSponsor\Accounts\Account\TimePeriods\TimePeriod\PersonalRateOfReturn node will no longer be returned in the response for this new version of the service. |
8.1 |
10 |
Ensure that the VM Transaction History V4 web service no longer returns PRR data for a participant when the GetSummary operation is called by sending valid or invalid Participant SSN and Account ID as request |
11 |
Verify and crosscheck whether the VM Transaction History V3 web service still returns PRR data whereas the VM Transaction History V4 doesn't |