New Relic Log for Load Test carried on Local Performance machine on 16 June 2016:

https://rpm.newrelic.com/accounts/1353506/applications/24434194/transactions#id=5b225765625472616e73616374696f6e2f5743462f574f524b54455252412e49436f6e74726f6c6c6572417070546965722e476574436f6c6c656374696f6e222c22225d&tab-detail_177be78-4bd03df4-33d5-11e6-8eb5-f8bc12425d4c=database_queries&app_trace_id=177be78-4bd03df4-33d5-11e6-8eb5-f8bc12425d4c

Hi Saurabh Sablaka,

As per my analysis, this SP is getting called from multiple pages from multiple times. I have attached excel sheet for different calls and reasons for that. OEMODE_EffectiveDateCalls.xlsx

There are unnecessary calls from landing page for benifit types and for different plans. We can reduce these calls by only selecting those benifit types which are selected on EDS instead of all benifit types and calls for different plans by checking whether plan level rule is set or not.

Hi Rakesh Roy,

I have checked in Generic Effective Date SP changes into LB. On landing Page there were almost 102 calls for this SP, now we have reduced it to the 12 calls. I have attached different Test cases Test Cases.xlsx which i Have verified during Unit testing. Cobra Enrollment unit testing is remaining because of some problems but i have verified for other enrollment modes.

As this is the major change for workflow, Please make sure that it should be tested thoroughly. We need to test attached test cases and following mentioned scenarios.

1. Qualifying and Plan Wise enrollment mode running at a time for a user
2. Different Plan wise enrollment for different benefit Types.

CC: Satya Saurabh SablakaSamirVijayendra ShindeAmruta LohiyaPrasanna Karlekar

Hi Rakesh Roy,

Cobra Enrollment Unit testing is also done locally. It is working as expected. I have attached updated test cases for it.

Test Cases.xlsx

CC: Saurabh Sablaka Prasanna Karlekar Samir Satya Suhas Joshi

Will be able to start the testing once the company is taken down on LB for testing.

Hi Vikas,

I have downloaded ASMl from Stage to LB and created scenarios on both Stage and LB.
Scenarios covered:
1. New Hire Employee
2. Open Enrollment Employee

For both cases the stage and LB workflow pages mismatched.
New Hire: Stage | LB 9 | 165
OE: Stage | LB 5 | 10

Company Name: On LB: DONOTUSE_CALLSTESTING and Stage: Asml for Hspl

As there is inconsistency in both scenarios assigning to you. Please assign back to me once the issue is resolved.

Hi Priya,

This was due to EDS screen was not saved on Stage. I have saved it. Please check now.
Assigning ticket back to you.

The above enhancement is tested by Partner, Admin and Employee work flow on LB. The before patch work flow and plans are noted from Stage.

Before Testing Readings
Environment: Stage
Company: ASML for Hspl
Workflow Testing by Partner, Admin and Employe

After Testing Readings
Environment: LB
Company: DONOTUSE_CALLSTESTING
Workflow Testing by Partner, Admin and Employe

Scenarios tested for OE, New Hire, ReHire, Classwise OE, Planwise (checked for Medical Plan only), COBRA and Dependent Audit.

Attached are the scenarios [work flow] covered during testing and also a text doc is attached which has list of employees with UserID, Password and SSN.

As per the testing all the work flow tested are having same Plan and no. of pages in tunnel. So, moving the jira on Stage.

The enhancement is verified on Stage Hspl company.

Environment: Stage
Company: ASML for Hspl
Workflow Testing by Partner, Admin and Employee

Scenarios tested for OE, New Hire, ReHire, Classwise OE, Planwise (checked for Medical Plan only), COBRA and Dependent Audit.

The before patch ratings for Production are noted.

The excel for the same is attached with jira. As workflow pages and plans are matched. We are moving the jira on Production.

I have started testing the patch on Production for ASML for Hspl company.

Environment: Production
Company: ASML for Hspl
Workflow tested for OE and New Hire Employee

for workflow number of pages and plans available for enrollment are exactly same. Will be continuing testing for other workflows tomorrow.

Environment: Production
Company: ASML
Workflow Tested: QE, Plan wise, ReHire, Classswise and Dependent Audit

For all the work flow tested number of pages and the plans eligible were same. Flows covered on Production are listed on excel and attached with the jira.

The before patch readings are same as that after patch reading on production. So, closing the jira on Production.