Hi Satya,

Please find estimates in an attachment. [^WT- 3274 estimations.xls]

cc: Jyoti Mayne shyam sharma

Considering my planned leaves in next week and changes [which may come after Amruta's suggestions], code review date is provided.

Amruta Lohiya Abhijeet Khandagale : This is from last sprint i..e from Sprint 7 why still this is In-Progress. Ideally by this time this should complete. Please speed up on this task.

Hi, shyam sharma

As I was on sick leave for 2 days, and this enhancement has major impact on existing system, it took more time for devlopment. We are done with this enhancement and code review. We have checked in the changes in local branch. We will check in these changes in LB branch after Stage build.

CC: Amruta Lohiya Jyoti Mayne

Abhijeet Khandagale Amruta Lohiya : is this now moved to LB ? as still I can see this task in Progress in Sprint 7 dash board.
if yes please update ticket status.

Hi shyam sharma,

LB and Stage branches are separated today. We were not supposed to do check-in new enhancements in LB branch till branches were together that's why this was not pushed to LB. We will push code to LB today. I will update ticket once it is deployed on LB.

CC: Amruta Lohiya Jyoti Mayne

Abhijeet Khandagale Kindly share analysis document for the same.

Deepali Tidke, Please find attached analysis document. 3274.doc

Hi Amruta Lohiya,

This is deployed on LB.

kindly start writing test cases for the same.

Abhijeet Khandagale Amruta Lohiya : as discussed kindly help us with the impacted area to be checked.

PFA Test Cases

Added Hrishikesh Deshpande and Aniruddha Dev for export part verification

Deepali Tidke Rakesh Roy : what is testing plan for this task ? when this will move on stage and Prod as this task is from Sprint 7 and not moving ahead.

shyam sharma - Testing is in progress for forced contingency. We have found two issues WT-3902 and WT-3905 ones we got LB deployment date of those issues we can update stage and production due date.

Found two issues in Forced Contingency - WT-3959 and WT-3960

Amruta Lohiya : This task from sprint 7 is still pending, please let me know who is working on - WT-3959 and WT-3960 ?
and by when we could complete this task ?

shyam sharma
As I mentioned, we have changed the major logic and its regression is in progress. We have assigned reported issue to Jyoti and she is working on it. Friday EOD we will update status again.

Girija Potdar

As per our discussion, please look into this issue. Contingency + pending scenario should work.

Girija Potdar Any Progress in last 5 days?
CC - Amruta Lohiya

Hi shyam sharma,

We are done with the development, but Unit testing is pending. We will deploy this on LB by tomorrow after thorough testing.

Thanks.

Girija Potdar : 6 days gone .. what is current status of this task ? what is pending ? please update JIRA ticket
Amruta Lohiya

Hi shyam sharma,

I couldn't work on this for the last two days as I was working on WT-4650.
Will resume development on Monday(9/12/2016).

Thanks.

Hi [~meghana.kulkarni],

As discussed with you WT-3959 is fixed. WT-3960 needs to be discussed with Amruta and the rest of the issues are 'can wait'.

Please verify all the scenarios:
Normal+Normal
Normal+Pending
Pending+Normal
Pending+Pending

Consider these cases for Benefit and Plan level Eligible & Forced Contingencies.
Also verify by changing tiers and plans within same benefit type.
Let me know if you need more details on this.

Thanks.

Added Hrishikesh DeshpandeAniruddha Dev for Export part verification

CC - Rakesh RoyDeepali Tidke

Will update testing status ones reported issue [ wt-4831] is deployed and verified on LB.
Rest of attached test cases are working fine.

Assigning to Hrishikesh Deshpande for export part verification on LB

Export scenarios are tested and those are working as expected. Will again test scenarios after fixing existing issues on lb.

Verified basic scenarios on stage >> working fine

Hrishikesh Deshpande kindly check export scenarios on stage, once completed please make it ready for production.

Verified below scenarios for EXPORT on stage on UND for HSPL Company on QE Illusions Banner Payroll 2016 file. For normal and pending review changes elections. Considered these scenarios for eligible and forced contingent plans

1) New Hire Enrollment
2) Open Enrollment
3) QE- Dependent spouse or child obtains insurance (Coverage Tier and Plan Change)
4) Terminate Plan Elections
5) QE- Child Birth or Adoption or Granted legal guardianship (Coverage Tier and Plan Change)
6) QE- Admin Change

Result: Scenarios are working as expected and records exported on the file are proper with proper Election change reason of Review Pending and QE date of Review Pending. Ready for Production

CC:Hrishikesh Deshpande Amruta Lohiya [~meghana.kulkarni] Deepali Tidke Girija Potdar

Verified below scenarios for EXPORT on stage on UND for HSPL Company on QE Illusions Banner Payroll 2016 file.

1]Normal enrollment with Qualifying event show On Exported file
2]Normal enrollment with Review Pending:Accepted then Qualifying Event show On Exported
3]Normal enrollment with Review Pending:Rejected then record is not exported

4]Exact tier + forced contingency enrollment with Qualifying event show On Exported file
5]Exact tier + forced contingency enrollment with Review Pending:Accepted then Qualifying Event show On Exported
6]Exact tier + forced contingency enrollment with Review Pending:Rejected then record is not exported
7] Coverage Tier and Plan Change :
8]Terminate Plan Elections
9]QE- Admin Change
10] QE- Dependent spouse or child obtains insurance
11) New Hire Enrollment
12) Open Enrollment
Working fine as expected.

CC: Rakesh Roy, Hrishikesh Deshpande,Aniruddha DevAlankar Chavan[~meghana.kulkarni]Amruta Lohiya

Hello All,

Enrollment side testing is done on Production - working well. Please have a look on tested scenarios -

Benefit Type Contingency - Eligible if enrolled in any selected benefit type
Benefit Plan Contingency - Enrollment required if enrolled in any selected plan

—————————

Verification required set as yes on both of the plan (verification required Yes for the enrollment flow - NH)

enroll in medical with EE + SP

• medical as well as dental went for approval
• if both accepted - both got enrolled in EE+SP
• if both rejected - no enrollment in any plan
• if I reject medical first - dental got rejected automatically
• if I accept medical first - dental got accepted with same tier automatically
• if I accept dental first and then medical - both enrolled with same tier
• if I reject dental first and accept medical later - both have enrollment in same tier

• if I waive dental - dental waived - medical enrolled
• if I waived medical - dental got waived automatically

• if you try to enroll in dental with different tier as that of the medical one - system gives the validation message about exact tier condition enrollment

—————————

Verification required set as Yes on Medical (no verification on Dental)

enroll in medical with EE + SP

• medical as well as dental went for approval (I was accepting only medical will go for approval - need to confirm) - if medical rejected - dental rejected and if medical accepted - dental accepted
• if both accepted - both got enrolled in EE+SP
• if both rejected - no enrollment in any plan
• if I reject medical first - dental got rejected automatically
• if I accept medical first - dental got accepted with same tier automatically
• if I accept dental first and then medical - both enrolled with same tier
• if I reject dental first and accept medical later - both should have enrollment in same tier

• if I waive dental - dental waived - medical enrolled
• if I waived medical - dental got waived automatically

• if you try to enroll in dental with different tier as that of the medical one - system gives the validation message about exact tier condition enrollment

—————————

No verification on any plan

enroll in medical with EE + SP

• if I enroll in medical - dental gets enrolled with the same tier
• if I waive medical - dental gets waived too
• if I change medical enrollment tier and enroll again - dental gets enrolled with the same tier

• if I waive dental - dental waived - medical enrolled
• if I waived medical - dental got waived automatically

• if you try to enroll in dental with different tier as that of the medical one - system gives the validation message about exact tier condition enrollment

—————————————

Benefit Type Contingency - Eligible if enrolled in any selected benefit type
Benefit Plan Contingency - Eligible if enrolled in any selected plan

———————

No verification required on any plan

enroll in medical with EE + SP

• if I waive medical - dental gets waived too
• if I enrolled in medical - dental gets available for employee and system restricts employee to enroll in dental with the same tier as that of the one in medical
• if you enrolled in medical and dental with E - now you change medical tier to E+SP and enrolled - system automatically enrolls employee in dental with same tier as that of the medical one i.e. EE+SP

• if I waive dental - dental waived - medical enrolled
• if I waived medical - dental got waived automatically

• if you try to enroll in dental with different tier as that of the medical one - system gives the validation message about exact tier condition enrollment

—————————

Verification on both plans (Verification required as Yes on enrollment flow - NH)

• enrolled in medical - and this request is rejected form pending queue - employee do not get dental plan too
• enrolled in medical - request accepted - employee gets dental - system restricts employee to enroll in dental with the same tiers as that of the one in medical.
  if enrolled in dental - dental request goes for approval and enrollment gets added or rejected as per the request accepted or rejected from pending queue
• medical and dental has enrollment with same tiers. I changed medical tier and enroll - medical as well as dental went for approval - whichever action I do with parent (accept / reject) same reflected to dental - if accepted the request, both enrolled with same tier - if rejected the request, older enrollment with same tiers persists

• if I waive dental - dental waived - medical enrolled
• if I waived medical - dental got waived automatically

• if you try to enroll in dental with different tier as that of the medical one - system gives the validation message about exact tier condition enrollment

—————————

Verification required set as Yes on Medical (no verification on Dental)

• enrolled in medical - went for approval - if rejected - dental also gets ineligible
• if enrolled in medical - went for approval - if approved - dental gets eligible and system restricts employee to enroll in the same tier as that of the medical.
  with the same tier employee can enroll in to dental without sending request to approval
• medical and dental has enrollment with same tiers. I changed medical tier and enroll - medical as well as dental went for approval - whichever action I do with parent (accept / reject) same reflected to dental - if accepted the request, both enrolled with same tier - if rejected the request, older enrollment with same tiers persists

• if I waive dental - dental waived - medical enrolled
• if I waived medical - dental got waived automatically

• if you try to enroll in dental with different tier as that of the medical one - system gives the validation message about exact tier condition enrollments

—————————

Verification required set as Yes on Dental (no verification on Medical)

• if enrolled in medical - no approval - dental gets eligible
• system restricts employee to enroll in the same tier as that of the medical in Dental. With the same tier employee can enroll in to dental - request goes for approval - if accepted the request, dental enrollment done with the same tier as that of the Medical - if rejected the request, no Dental enrollment exists

• if I waive dental - dental waived - medical enrolled
• if I waived medical - dental got waived automatically

• if you try to enroll in dental with different tier as that of the medical one - system gives the validation message about exact tier condition enrollments

—————————

Basic scenarios out of above are also tested with ‘Require tier/coverage match up’ set as NO
It worked well - in case of employee wants to enroll in Dental with different tier than the Medical - system allowed him to do so which is expected.

—————————

I have observed a new issue WT-5348 and assigned it to Satya. I am not sure whether this is because of the above enhancement - hence not linking it to this ticket.

—————————

As per the discussion, Exact or Less tier matching scenarios have not been tested as the issues for the same are still opened. All scenarios needs to be tested once those are fixed and available to test.

CC - Deepali Tidke Rakesh Roy [~meghana.kulkarni] Rashmita Dudhe Priya Dhamande Aniruddha Dev Hrishikesh DeshpandeAmruta Lohiya