workday 2020r2 testing updates in a changing world · • 5-week preview period • regression test...
TRANSCRIPT
Workday 2020R2: Testing Updates In A Changing World Tuesday, 18th August 2020
Stacey Zito
Senior Support Engineer
Carol Buie Colin Truesdale Lauren Kerr
Customer Success Manager
Product Manager Testing Technical Lead
Kainos & WorkdayWe’re all-in on Workday – Kainos is the leading providerof Workday services and test automation
Developers, Workday Consultants, Product Leads400+ Workday experts
Launched in 2014Smart
WorkdayGlobal Partners since 2011 900+ Certifications
Workday Certifications
Coming up…
Workday HCM: What's New In
2020R2
AUG 25th11AM EST
Workday FINS: What's New In
2020R2
AUG 27th11AM EST
Workday update strategy
Before we begin : Update Testing 101
Regression testingDue diligence checks to ensure that any software updates or configuration changes on Workday don’t have any adverse effect
Twice-yearly• New versions of Workday • On your Production tenant in March / September• 5-week preview period
• Regression test your configuration• Investigate new features
Weekly• Sandbox refreshed with configuration
and data from Production• Updates applied• Regression test to catch any issues
When to test
Major Workday Updates
Weekly Workday Service Updates
Integration ProjectsChanges to upstream & down stream systems
New Workday Modules
Business ExpansionMergers/Acquisitions
DivestituresNew Territory
Configuration ChangeBP DefinitionsSecurity Configuration
When to test
Testing updates
4 key questions when testing updates
Can your users still do everything they used to?
Can your users still NOT do anything they shouldn’t be able to?
If not, why not? And how do we fix?
If not, why not? And how do we reinstate?
What should we focus testing on? - Eric
SecurityHCM :
Hire-to-retire, comp eligibility
Financials : Procure-to-pay, Account Posting
Rules
Payroll calculations
Payroll -> Accounts Integrations
How big should my regression test suite be?- Jamal
75 HCM security scenarios across user-based, role-based, key workers
100 HCM end-to-end BP scenariosacross create position, hire, change job, change comp, terminate
20 integration tests against your priority integrations
20 custom report tests on report availability, structure, data
75 FINS security scenarios across invoices, companies etc.
200 critical FINS scenarios asset, procurement, revenue and expense management, accounting
35 E2E Payroll scenarios representing the lifecycle and pay of synthetic workers
Based on 10k FSE10-50k FSE - add on another 50%50k+ FSE – double it
How big a team?
HCM testing+ BPs + Security + Integrations + Reports
= 80-100 man-days
3 full-time testers for 5 weeks
Focused period week 1 & 2 then less
Larger group one day per week
or free up time by automating it
What should we test and when? - Grace
Week 1 Week 2 Week 3 Week 4 Week 5
SecurityReports
Integration
BPsSecurityReports
Integration
SBX-PREVIEWAVAILABLE
REQUESTREFRESH
RELEASED TO PRODUCTION
BPsSecurityReports
Integration
BPsSecurityReports
Integration
BPsSecurityReports
Integration
Important: regression test again on your Production SBX
on ‘Week 6’
Test
team
Test
lead
Con
fig
team
WD
Start Run test scenarios
Mark test as passed
End
Retest Defect
Log in defect tracker and assign
Scenariopassed?
Defect exists?
Triage defect
Create assistance ticket
Update status in defect tracker
Close defect in tracker
Functional defect
Technical defect
End
Investigate & Fix
Update defect log
Investigate & Fix
Update defect log
Y
Y
Y
Y
Ongoing use of your Preview tenant
Preview tenant is always available
Early sight of upcoming features
Candidate features only – not confirmed until start of preview period
Front-load your new feature adoption effort ahead of preview
What’s your advice for introducing and testing optional changes? - Jennifer
Impact analysisHow do we communicate and introduce the change?
Test planDoes this change require a separate test plan?
Go / No-go decisionCan this feature be safely included and bring value?
Roadmap of innovationMove on to the next new feature!
Automate testingFree up time to look at other features or perform change management.
Project planningIs this change big enough to need a project stream?
How do you take compliance into account when testing? – Ken
Manual testing = data exposure risk
Create safe supervisory orgs for
testing in
Assign testers to your new test orgs
Test against synthetic workers, not real workers
What are some considerations we might not be thinking regarding testing from home?
Ensure the right tools for handling sensitive dataVPN, SFTP etc
Data handling / cleanup traininge.g. always deleting data from local machine when not actively using it
Regional testing leads with strong product knowledgeGood contact with local SMEs to know the variances
Calendar-based testing sessionsEnsuring SMEs / test leads are available
Frequent stand-upsand social contactReviewing defects, test plan updates
Redundant testingMultiple testers reducing the risk of incorrect test results
How do we test updates during deployments and projects? - Rick
How does the preview period align with your testing events?
Combined test eventRequest implementation preview tenant
Test in preview
Separate test eventsPerform implementation test as normal
Perform full regression testing on preview
Test event and update preview overlap
Implementation test event
Update preview period
Test event and update preview don’t overlap
Impl testUpdate preview
Any advice on the days after the release?- Kim
2. Review feature delay notifications
3. Configure new required and optional features
4. Customer feature release checklist
1. Run a suite of sanity tests in Production
6. Keep adopting new features!
5. Preview Center -> Release Center
7. Prepare for retirement (of features)
8. Continually review service update notes
9. Check What’s New for new features in Preview
10. Celebrate with your team!
Testing your changing world
There’s a lot of rapid change in our Workday happening at the minute – everyone is
making suggestions!
How do you know what the right thing to do is? - Marcie
A world of change
CompensationHealth information
LocationsTeam structures
Job changesSecondmentsAbsence rules
Office Work from home
Blended locations
Backing out changes‘New normal’ modifications
BAU changes
How much testing are you currently doing on urgent changes?
59%24%
5%12%
Every change is tested in SBXbefore promotion to ProductionMost changes are tested in SBX,small ones aren'tOnly higher-risk changes aretested, most aren'tNot using SBX much at present -mostly changing Production
STEP 2Make config changes on Sandbox
STEP 3Review & check changes
STEP 1Analysis
STEP 6Release to Production
STEP 5Sign Off
STEP 4Regression Test
The change release cycle
Regression Test with Kainos Smart
Run Regression Test Pack
Did tests fail?
Was it Expected
?
Proceed
Re-baseline Test Pack
Investigate and Fix Workday
NO
YES
YESNO
STEP 4Regression Test
STEP 3Review & check changes
STEP 5Sign Off
Test your Workday configuration every week
Reducing your testing effort
Workday-certified experts
Test execution and triage
Scope and build test cases
Application Management Services
Test automation
How do I perform my normal regression and update testing during the preview period – I don’t have time! – Petra
Business Processes, Security, Integration Integrity
Business Processes & Security
Preview Security & Integration Integrity
In Sync(week 1, week 5*)
Not in Sync(week 2-4)
Preview TenantSandbox TenantPreview Sync Status
Tenant-to-Tenant Tests (reports, integrations, Parallel Period Payroll)
* Refreshed upon request to Workday
How much can you realistically get done each week?
Automate it.
Free test plan assessment
Effectiveness of your WD2020 r2 strategy
Recommended strategy and changes for WD2021 r1
Limited spaces – book now via [email protected]
Coming up…
Workday HCM: What’s New In
2020R2
AUG 25th11AM EST
Workday FINS: What’s New in
2020R2
AUG 27th11AM EST
