Finance Unit Testing

The Finance team rang in October by starting its next big phase of the implementation, Unit Testing. Unit Testing is a very important part of any software development because it focuses on making sure the smallest testable "units of things" can be tested. In a Workday implementation, that means making sure members of the team can do each invididual process. We aren't focusing on seeing a process through from start to finish, just making sure that each of the individual pieces work from multiple angles and perspectives. It's a bit like making sure all the individual ingredients of our recipe are accounted for and are in good condition before we start assembling the whole dish. 

Our implementation partner Alchemy provided the team with a massive spreadsheet of testing scenarios, and the Bowdoin team then went through and added their own processes to the list. Unit tests have been assigned to team members, and they log in to our implementation tenant to attempt to, for example, create a customer contract or create an ad hoc payment. If the tests go as planned they are logged as successful tests! Those are, of course, the best kind of tests. But sometimes an unexpected result or an error pops up, or someone can't see part of the process they thought they were supposed to be able to see, and then the team logs an error or a defect and calls it to the attention of their Alchemy consultant, who can provide a fix or suggest that the team discuss it in their next meeting. 

This unit testing will continue on through the end of the year, with our Bowdoin and Alchemy teams continuing to meet weekly - sometimes multiple times weekly! - to continue to learn, test, and adjust our Workday instance together.