Tested below points on Azure Workterra application:

• Employee management
• Employer management
• Add Employee
• Employee Self Serve Mode(OE)
• Import/Export – Manual Export

getting ‘URL not matching’ error while creating candidate profile using career integration link, to verify Recruit, Pre-board, Onboard etc.

I checked below points on Azure workterra site and are working fine.

• Recruit: Create Candidate, create candidate profile, schedule interview, hire candidate.
• Pre-board tour
• Onboard tour
• New Hire SSM

Also, while creating candidate using LinkedIn credentials I’m getting server error.

Received Users list from Ashwin. Data Validation for load testing in progress.
Reported below issue regarding test data, to the dev team.

Getting pre-board tour to all the employees. Please change the settings so that all employees will get the OE self serve mode.

Mailed login issue to Ashwin Wankhede for Azure environment.
Sent the data reset queries to Ashwin for update according to new company on Azure.

Started the role based testing on Azure Environment for UK benefits Company

Traversed below features on Azure environment for UK Benefits company using company admin login.

• Employee management
• Employer management
• Add Employee
• Employee SSM
• Import/Export
• Customizer
• Recruit
• Add Candidate
• Manage Candidates

While testing the career integration feature, we were unable to login to the system with both LinkedIn credentials & candidate login credentials.

Verification of the Role based testing on the Azure Environment for UK Benefits company.
Follow up with Ashwin regarding the Company setup.

Follow up with Ashwin regarding the new company setup other than UK benefits.

Performance Team meeting
Data Validation for Wheaton on Azure Envirironment

Data Validation in progress.
Provided ideal user to replicate settings to all users of Wheaton

1. Performance Team meeting

2. Started with data validation on the Wheaton Company

1. Data validation for Wheaton company
2. Added plans to the employee
3. Discussion with Ashwin regarding the observed descripincies

Data validation and and discussion with Ashwin regarding the issues.

Data Validation in progress. Provided discrepancies to Ashwin.

1. Follow up with Ashwin regarding the Employee settings
2. Data validation for some of the employees to identify the descripency.

Data validation on the Wheaton client to find-out the further Discrepancies in the data.

Performance Testing related follow up with Dev team for data validation issues.

Follow up with Ashwin regarding the Self serve mode issues

Performance Testing related follow up with Dev team for data validation issues.
SVST study

Follow up with Ashwin regarding the Self Serve mode issue

1. Providing data to ashwin for the self serve mode
2. Discussion with Ashwin and developer regarding the Self serve mode issues
3. Data verification

Performance Testing related follow up with Dev team for data validation issues.

Worked on verifying the server error & other issues reported found while data validation for Wheaton.
Provided with the ideal user to replicate same settings for all other employees of Wheaton

1. Data validation for the Employees
2. Discussion with Ashwin regarding the Issues we encountered during data validation

1. Data Validation after making changes in the Employee Settings

Data Validation in progress:

Verified the discrepancies salved by Dev team. Below issue is still not fixed.

We have found 1 discrepancy in the employee SSM pages after data reset.
Below 2 plans are already enrolled for most of the employees.

Page 10: Enroll Now Basic Life- Regular or Religious or Seasonal Worker or Academic
Page 11: Enroll Now Basic AD&D - Regular or Religious or Seasonal Worker or Academic

For below users, these plans are not already enrolled.

1. aadeb481983033
2. cande399766989

Because of this issue we are getting different count of plans on the Beneficiary page
(page 19).

1. Data validation After resetting the Data
2. discussion with Ashwin regarding the discrepancy issues we faced during the Data validation

Completed Data Validation for Wheaton on Azure environment.

1. Data validation as per the latest changes
2. Discussion with Ashwin regardin the Application issue and follow up
3. Script recording

Completed Script recording for Wheaton on Azure environment.

Got 404 Not found errors for multiple jpg & png files. Reported the issue to Dev Team

1. Script Parameterization for Azure Environment

Performance test script recording
Script Parametarization

1. Parameterization on Azure Environment
2. Dry run on the azure environment with 10 users followed by 200 users

Load test pre & post test activities.
Load Test executed for 200 user load. Created and shared results through email.
Error Analysis in progress.

Internal Discussions and R & D for Hearder Record in VSTS

Executed 500 user load test on Azure environment.
Error analysis in progress.

executed 200 user load test and shared the results.
analysis done for Request timed out errors & implemented solutions which were helpful in removing the Request timed out errors.

1. Test Execution on Azure environment
2. Disucssion with aniruddha regarding the issues faced on Azure environment

Executed 200 user load test for which 91% success rate was achieved. Shared results for the same.
Executed 500 user load test which was aborted by VSTS due to high count of 'System.out of memory' exception.
Analysis in progress for above mentioned error.

Azure:
1. Executed the 200 users test on Azure and analyzing the failures encountered during execution.
2. Discussion with Aniruddha regarding the failures encountred during execution

Executed 500 user load test and shared results with team.
Analysis done for 'System.out of memory' exception.

Implemented solutions were helpful in removing above mentioned error.
Analysis for Web Test Exception & Socket Exception is in progress.

1. Analysis of the 'System Out of memory' issue on the Azure Environment
2. Execution of the 500 users test along with changes in the Connection pool setting
3. Execution of the 500 users tests by making changes in the System Arch settings to x64

1. Data validation on the Azure environment
2. Script parameterization for Azure Environment
3. Executing the 200 user load test
4. Analyzing the results of the load test
5. Sending the Load test report

Executed 500 user load test on Azure environment. Share test results with stake holders.
Error Analysis for Azure load test.
Pre & Post test activities

1. Load test with 500 users on the Azure environment
2. Sending report of the load test to leads
3. Analyzing the Performance testing results on Azure

Executed 500 user load test on Azure environment. Share test results with stake holders.
Error Analysis for Azure load test.
Pre & Post test activities

Error Analysis for Azure load test.
Implemented chages to avoid web test errors, time out errors etc.

1. Data verification on the Azure environment after upgrading the Azure build
2. Dry run with the 1 and 5 users on the updated Azure environment
3. Execution of 500 users test on Azure environment
4. Analysis and sending report to leads

Error Analysis for Azure load test.
Pre & Post test activities

1. Analysis of the 500 user load test executed on the 23rd March

1. Finding out the page response time of the New UI (US Azure Workterra site) from EBS network

1. Finding out the page response time of the New UI (US Azure Workterra site) from EBS network
2. Shared the results with Leads

1. Analysis of the newrelic setup on the US Azure Machines
2. Dashboards to identify the CPU And Memory were not configured on the Azure machines, so pointed out the same to Indra
3. Analysis of adding new dashboard for CPU and Memory for the configured servers
4. Discussion with Indra regarding the adding the new Dashboard for CPU And Memory

1. Verification of the Azure machines setup by Indra:

a. Setting up the VSTS on the Azure machines
b. Comparing the new Azure Machine Setup by Indra
c. Comparison of the VSTS installed on the Azure machines setup by Indra and the SEZ controller machines
d. Verification of the availability of the SQL Server Management Studio’ installed on the US Azure Load Test machine, to access the load test database on this controller.
e. Discussion with Indra regarding the setting up the New Azure Machine

Verification of the new two machines setup by Indra for Azure

1. Discussion with Anirudha regarding the US Azure Load testing

1. Following up with Ashwin regarding the Us Azure setup

1. Data validaton on the US Azure Environment
2. Restting the data before starting the Script repording
3. Performance Script recording for US Azure Environment
4. Parameterization of the recorded Script

1. Parameterization of the Performance Script recorded for the US Azure Environment
2. 10 Users dry run on the US Azure Environment
3. Analysis of the Dry run
4. Executed the 250 Users Load test
5. Analysis of the 250 Users Load test results
6. Sending results to Leads

1. Analysis of the Performance Counters on the US Azure machine for 250 user load test
2. Documenting the results
3. Sending the reports to Leads

Error analysis of 100 user load test on US Azure environment.

1. Discussion with Samir, Indra, Anirudha and Ashwin regarding the Us Azure Results and the future tests to be conducted
2. Dry run on the US azure environment
3. Conducted 2 rounds of 100 Users load test on US Azure Environment

1. Conducted 100 User 3rd load test on US Azure Environment
2. Analysis of the all three tests of the 10 Users Load tests
3. Sending the report (Partial) to leads.
4. Started Analysis of Perfmon counters for all tests on the US Azure Environment,

1. Analysis of the 100 user load test executed on previously
2. Preparing the report for the 100 user load test
3. Sending the Report to Leads

1. Analyzing the Results of the 200 user load test

1. Resolving the issues on the GP controller
2. Trouble shuutting the GP controller setup and trying out the solutions for the controller

1. Dry run on the GP controller to ensure that the GP controller is up and running.
2. Executing the 50 and 100 user load test on the GP Controller to ensure that the GP Controller is working fine

1. Exection of the 200 user load test on Us Azure Environment
2. Exection of the 300 user load test on Us Azure Environment
3. Analysis of the failures happened in the 300 User load test on US Azure environment

1. Execution 300 user load test.
2. Analysis of the results

1. Execution 300 user load test.

1. Analysis of the 300 User load test report
2. Sending the report to the Loads

1. Preparing the perfmon couter graphs and page load time details
2. Sending the permon counter detials and page load time to leads

Analysis of the test results.

1. Conducted 300 user load test on US Azure
2. Analysing the results of the 300 userload test
3. Analysis of the 300 user load test results

2. conducted 300 user load test on US Azure
3. Duscussion with N&S team regarding the bandwidth usage of during the 300 user load test execution
4. Analysing the results of the 300 userload test
5. Sending the 300 user load test report to leads

1. Execution of the 300 user load test on the US azure Environment
2. Following up with N&S team regarding the utilization of the network bandwidth during the test execution
3. Analysing the results of the 300 userload test
4. Discussion with UK regarding the performance test plan

1. Followup with ashwinregardin the Web Server Access
2. analysing the results of the 300 userload test
3. Sending the results of the 300 user load test.

1. Execution of the 200 user load test on the Azure Environment

1. Conducted 2 200 user load tests o nUS azure Environment
2. Discussion with Nandu regarding the user logout issue at the end of the load test
3. Analysis of the the user logout issue at the end of the load test

1. Analysis of the issues encountered during exection of the Load test
2. Execution of the Load test to identify cause for the Load test hand issue
3. Data validation of the SSM on gthe US Azure load test company
4. Making some changes in the Plans to get displayed in the SSM

Performance team meeting and issue/query analysis with Shailesh.

1. Load test script recording on the US Azure.
2. Parameterization of the script.

Performance team meeting and issue/query analysis with Shailesh.

1. Traversing the SSM manually
2. Encountered the Issue during submitting the plans.
3. Reported same issues to Ashwin and Dev team.

Performance team meeting and issue/query analysis with Shailesh.

1. Preparing the Script and parameterizing
2. Dry run with user load 20, 50, 200 and 100
3. Analysis of the failures during the 200 and 100 user load test
4. discussion with Nandu regarding the issues we faced during the dry run

Performance team meeting and issue/query analysis with Shailesh.

1. Script Recoring and Parameterization
2. Dry run on the recorded script.

Performance team meeting and issue/query analysis with Shailesh.

1. Webtest script recording and Parameterization on US Azure Environment for Company'Wheaton Franciscan Healthcare For Load Testing'.

Performance team meeting and issue/query analysis with Shailesh.

1. Dry run on the Script Recorded on 10th July
2. Analysis of the failures encountered in the Dry run.

Performance team meeting and issue/query analysis with Shailesh.

1. Meeting with Samir, Nandu and dev team regarding the Us Azure tests
2. Opened the tickets regarding the new creation of the new Controller at SEZ location
3. Opened ticket to reclaim the GP Controller machines.

Performance team meeting and issue/query analysis with Shailesh.

1. recorded the WebScript on US Azure as previous web Script failed due to new addition of the images.
2. Parameterization of the WebScript
3. Dry run of the Parameterized Script
4. Executed the 200 user load test

Performance team meeting and issue/query analysis with Shailesh.

1. Executed two tests of 200 User Load tests on US Azure
2. Result Analysis of the two executed scripts
3. Preparing the Load test report
4. Sending the load test report to Leads

Performance team meeting and issue/query analysis with Shailesh.

1. Executed 200 user load test on US Azure
2. Recorded WebScript on US Azure after the new build update
3. Parameterization of the new Script

Performance team meeting and issue/query analysis with Shailesh.

Performance team meeting and issue/query analysis with Shailesh.

Performance team meeting and issue/query analysis with Shailesh.

1. Analysis of the configuration of the Controller and Agents on the SEZ controller

Performance team meeting and issue/query analysis with Shailesh.

Recorded a performance test script on US Azure environment.
Conducted dry runs & validated the script.
Executed a 200 user load test with new script on latest build.

Conducted 2 load tests of 500 users on US Azure environment.
Started the result analysis

Load test result analysis for the 500 user load test conducted on 23 July on US Azure environment.
Share detailed analysis report along with

1. est results
2. error details
3. enrollment count
4. perf. monitor data along with CPU, memory utilization graphs for all servers.

Analysis of the errors found in the load tests conducted on 23 July.
Applied the solutions on the script and validated the script.

Conducted multiple load tests on US Azure environment for 100, 200, 500 user load.
Shared the detailed results of the 500 & 200 user load tests.

1. Discussion with Anirudha regarding the Tests executed during the leave period
2. Analysis of the results send by Anirudha
3. Script recording and parameterization.

Result analysis for the load tests conducted on 26 July.

1. Completed 2 rounds of 1000 user load test on US Azure (Company: Wheaton Franciscan Healthcare For Load Testing)

Result Analysis for the tests executed on 29th July

Meeting with Performance Improvement team regarding the results of load test executed on weekend.

Performance test result analysis with Nandakumar & Shailesh
Discussion about the performance execution strategy for future test executions

1. Analysis of 1000 user load test results conducted on 30th July

1. Triagging the issues faced on Agents for the Distributed load testing on Azure Environemnt

1. Triagging the issues faced on Agents for the Distributed load testing on Azure Environment

1. Follow up with Nandkumar and Ashwin regarding setting up the ASMl company for US Azure.
1. Data validation of the ASML company on US Azure

1. Preparing the Jmeter Script for Us Azure for Company Wheaton for Load Testing

1. Data validation of the Companies moved to US Azure

1. Data validation of the Companies moved to US Azure

1. Data validation of the Companies moved to US Azure

1. Data validation of the Companies moved to US Azure

1. Data validation of the Companies moved to US Azure

1. Data validation on the Us Azure for the Wheaton as we were facing some issues for the SSM for employees
2. Script recording for Load test on US Azure

1. Parametrization of the Us Azure Load Test Script.

1. Particularization of the Us Azure Load Test Script.
2. Dry run of the Load Test Script.

1. Following up with Network team regarding the bandwidth usage for the 500 user load test on US Azure environment
2. Dry run for the 50 user load on the US Azure Environment
3. Execution of the 500 user load test on the Us Azure Environment
4. Preparing the initial analysis of the 500 user load test on US Azure Environment

Analysis of 500 user load test.

1. Analysis of the 500 user load test for the Wheaton company
2. Preparing the Performance report
3. Sending reports to leads.

1. Analyzing the SSM by adding Spouse and child on the US Azure environment for Company Wheaton Franciscan Healthcare for Load Testing
2. discussion with Anirudha, nandu and Rakesh regarding the issue faced while adding the Spouse and Child
3. Reported issue related to Adding the child and Spouse in Jira

1. Following up with Sachin regarding the issues related to Child and SPouse on Us Azure
2. Identifying the New Scenarios those can be Recorded for Performance Testing

US Azure:
Exploring the Scenario for the SSM to generate the Load Test script on Us Azure

Us Azure
Exploring the Scenario for the SSM to generate the Load Test script on Us Azure

Us Azure:
Exploring the Scenario for the SSM to generate the Load Test script on Us Azure

Exploring the Scenario for the SSM to generate the Load Test script on Us Azure

Exploring the Scenario for the SSM to generate the Load Test script on Us Azure

Exploring the Scenario for the SSM to generate the Load Test script on Us Azure

US Azure: 2h
1. Validating the issue NF-4884 on the US Azure Environment

US Azure: 4hr
1. Recording the Us Azure Script for SSM mode.
2. Reported issue related to Adding Beneficiary in SSM mode.

US Azure: 5h
1. Validating the SSM scenario for SSM on the Us Azure for Load test company Wheaton.

Us Azure:
1. Recording the Webscript for US Azure for Load test compnay Wheaton
2. Start the Parameterization for the same script

Us Auzure:
1. Parameterizatoin for the us Azure Web Script

Script recording and parametrization for the US Azure

1. Execution of 1000 user load test on Us Azure Environment for Load Test Company Wheaton.

Analysis of the test execution results for 1000 user load test.

Analysis of the 1000 user load test on US Azure and sending the results.

Parameterization of US Azure webtest kipping the antiforgerytoken as true

Parameterization of the US Azure Load Test Script keeping the Antiforgery Token ON

Parameterization of the US Azure Load Test Script keeping the Antiforgery Token ON

Parameterization of the US Azure Load Test Script keeping the Antiforgery Token ON

Preparation of US Azure Load Test Script keeping the Antiforgery Token ON

Preparation of US Azure Load Test Script keeping the Antiforgery Token ON

Preparation of US Azure Load Test Script keeping the Antiforgery Token ON

Preparation of US Azure Load Test Script keeping the Antiforgery Token ON

Preparation of US Azure Load Test Script keeping the Antiforgery Token ON