When Workday releases an update, it’s a hectic time for its users as feature and functionality testing can take weeks on end. And there could be trouble if it’s not done right. Imagine the problems if people are not paid correctly or if there are mistakes in the calculations of leave days. To ensure that your Workday updates are integrated into the system as smoothly and efficiently as possible, follow these tips by our testing experts.

First up, understand why you need to test

Workday is a highly-complex workflow software that is integrated with many areas and processes within your organization, often interconnecting one department or process with another. Without proper testing, a tweak in one aspect of the software can indirectly affect another overlapping area – in the worst case scenario, even creating a domino effect in your configuration. You don’t want to be caught off-guard with glitchy systems that don’t perform as needed for your end-users.

Planning is essential

Workday updates have a fixed schedule with which you can plan your testing around. Make an outline of your team’s testing strategy a month or two before the preview period of the update. Decide what you will be testing and the resources needed for it. As soon as the preview window starts, you can begin testing, fully prepared.

Your plan should be detailed, determining who is doing what and at what time. Keep each person accountable to their testing area and communicate duties clearly to avoid oversights. Have a manager to oversee all aspects of the testing and ensure that it is going according to schedule.

Your plan should include:
– Notes on what risks to the systems you hope to avoid by testing, as well as the actual things you will do to avoid those risks.
– A clear idea of which staff is responsible for what areas of testing.
– The number of tests that will be conducted and the scenarios in which they will be undertaken to understand the effort that will go into testing.
– A testing calendar complete with dates, times and staff assigned for each testing.

Tips to strategize

1. Your testing strategy should be based around what features you plan to test. You will need to prioritize your testing according to the risks each area of processes poses on the entire system if something happens to malfunction.

2. Think about which processes will impact the business greatly if they stopped functioning as they should – it could be security functions or financial related processes, for example.

3. In your testing strategy, keep in mind the updates and feature enhancements that will have an impact on the current functionality you are making use of. Also think about the new features that you aren’t yet using yet and how they will make a difference to your processes and business once they are integrated into your Workday systems.

Be prepared for (some) failure

In every test cycle there are bound to be a few test failures so factor this into your testing plan. Add on some additional time that you will need to look into the problems, find fixes and record them for future reference, as well as run the tests again with the fixes.

Make a test script

Before testing begins, form a test checklist for each process you will be running a test for so that you have everything good to go with the time comes. This should include:
– Definition of what the test is and why it is needed
– Whatever is required by the staff in order to actually perform the test
– Which department the test is being run for
– Everyone involved or effected in the testing, including indirect links
– Steps to follow to undertake testing
– A clear conveyance of the result that is wanted from the test
– In case you are retesting from older tests, check whether your test scripts are up to date with current configuration

Tips to keep in mind to make manual testing easier

– Software updates from Workday appear in your Sandbox Preview Tenant over a five-week period. By testing your Sandbox and Sandbox Preview Tenants at the same time through this period you get to compare your running processes against the updated processes and see how each has been affected.
– Start by testing the functionalities that are most vital to your business. This is typically those relating to reporting, integrations and security. For organisations where there are a large number of integrations, automated testing with Genie is recommended as a seamless solution to the testing process.
– Move on to BP testing and Regression testing after as all the functionalities for BP will not be delivered until the first week is over. While running these tests, you can continue to work on previous testing as well as new functionalities are released.

Track & Log everything

Use tracking tools to make note of successes, failures and results – this is essential in manual testing. This data will provide a deep understanding and insights on what to do and what to avoid during your next testing cycle. Having records is also useful to show auditors and stakeholders when outlining your testing progress.

Make things easier next time

Breeze over the complicated steps involved in testing Workday updates with Genie, an easy-to-use Workday testing platform that runs tryouts in the background, without exhausting your company’s precious time and resources. Testing for entire processes, across tenants, can take a matter or just hours instead of weeks. Everything is logged and recorded and implementation is at the click of a few buttons.