I will answer the thread insofar as the Test component of the ReFramework is involved.
It’s is to offer a mechanism for the RPA developer to test pieces of their automation, aka develop Unit Tests.
It consists of the following components:
- _Tests.xlsx - a excel file containing a two sheets. On the first sheet is the list of paths for the workflows that will be tested and the expected output of the test. The second sheet contains the result of the test: for example if an AppEx is is the expected output for a test and the exception happens during the running of the test, it is a PASS.
- RunAllTests.xaml - the entry point to the test framework, this will run the files specified in _Tests.xlsx
- _Test.xaml - an empty example test. The reasoning why this file contains an invoke of the InitAllSettings.xaml is because, since we are invoking a list of totally unrelated tests, we need to make sure their Interface is the same (their input/output signatures must match). Notice the test is self-contained, meaning it has no arguments, for the purpose explained above.
So, for a brief review of how this works:
- Design self contained tests.
- Add them to the _Tests.xlsx file
- Run RunAllTests.xaml
The difficulty of designing your tests is precisely the fact that each one has to be self contained. Let’s consider that we want to test a part of a UiAutomation (the hardest example):
We need to do the following in the test:
- Obtain all of the values needed to open the Ui application (paths, urls and so forth)
- Open the application and navigate it safely up to the point we want to test.
- Test the respective section.
Obviously, there should be multiple tests for each section.
As for an explanation of what the practical exam entails with regard to the Test framework, I can’t answer that as I am not familiar with it.
Hope this helps