This solution is made to be used by UiPath developers to help them write better code and save them a lot of time when change requests occur.There are four main parts to this project:<ul><li>Framework&nbsp;used for automated running of unit tests and logging.</li><li>GUI specifically coded for this framework</li><li>Custom activity package&nbsp;that plays essential part in running of both Framework and Unit Tests.</li><li>Unit Test Template&nbsp;used to easily make Framework ready unit tests.</li></ul>My main inspiration was to help myself and other developers save time and effort that manual testing regularly takes, and which can be solved by automation (after all, we are automating processes, so why not a part of the development also?).A big reason too, was to bring UiPath development practices closer to the software development standards.

Tired of testing workflows manually? This framework for running unit tests will help ease the development and save time

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Senior RPA Developer

Preface: I really like the effort and structure but holding off on a review to make sure I understand some contexts. Please treat below as wanting to see it get better. The test runner itself looks nice, but it also does contain some things I truly don't agree with, so to be fair I'm posting this as a question instead of review to not skew the rating simply because maybe I'm missing some context. Main gripe is that by definition UnitTests must be self contained. In all of the examples and in the guide, you've omitted the Teardown phase completely. Due to that in NavigateToReddit example -> on failure window will stay open which may lead to other tests giving FalsePositive/FalseNegative results. Yes, it's an example, but it should even more stress how to write the test correctly. Second thing that stroke me was that in all of the examples the tested code is directly in the test (instead of invokes), which may lead people to believe that that's ok, while in reality it leads to desynchronization between tests and "real" code. Again, I know these are just examples, but since the framework and guide describe HOW to write UnitTests, it is relevant to not give bad example which people may build upon. A simple info that "In real tests _always_ use invokes to workflows under test" would be a good start if you don't have time to create examples with invokes. Next, there are some things in the Assert package that are, to me, confusing. Firstly - it contains Newtonsoft.Json directly instead of referencing it as a dependency for the package, which leads to size bloat and may lead to version conflicts. Secondly - there are .AreEqual and .AreSame implementations. At first I thought (since the methods don't contain XML comments - would be nice to have as well) "Ok, equal is a value comparison, same is a reference comparison, makes sense". But then in the examples string equality is checked using .AreSame (Strings are special, but they're still ref types even if behaving like value types most of the time). Could you clear this out? I might be missing something. Thirdly - AssertException, AssertNullException and CustomAssertException do not share a common base class. If you look at exceptions inheritance hierarchy in .Net a more specific exception always inherits from a more generic one, up to System.Exception. While this probably won't become an issue if using the framework as-is, it does seem to be an omission that could bite down the line. Fourthly - Assert class seems to be just a container for static methods, but is not static itself. For the documentation/guide: "For Framework to consider a Unit Test as valid, it must implement Assert Unit Test activity" That's nitpicking ;), but a workflow xaml does not implement an activity, it has one (is-a / has-a distinction). Your check is also xaml text based, which I also get why is like that, but ironically the ValidateTestFile.xaml also passes as valid unit test. Probably won't be a concern, but that's a possible issue. Sidenote - Why rolling your own Assert class? I admire the effort, but still - there are well tested and constantly supported libraries (MS UnitTesting framework, NUnit etc.). Or even use the built-in CheckTrue/False (they would provide same functionality as they throw CheckpointExceptions). Yes, the checks with need to be more specific with Check*, but "flexible" asserts seem dangerous (see above for value/ref comparison). It's also missing one of the IMHO most important things for UiPath testing - Assert.ThrowsException<T>.

Have you come up with a good way to mock activities in tests? For example let's say I have an Add Queue Item activity in a workflow file. There's logic in that activity that will output certain argument values if the Add Queue Item activity succeeds vs if it throws an exception. I want to mock that activity in my unit test to control what happens.Have you run into a similar issue? Mocking is very common in unit testing so this strikes me as something that's needed in a test framework.

hi Stefan, ima unable to access the PDF attached under Resources tab. Could you please provide any alternative link?...or send it to my mail ID....rameshgp43@gmail.comThank you

Hello!In this framework,For example, can the button on the browser be checked with the Click activity to see if it succeeded? I want to know that.Thank you.

Hi there,Is this project actively maintained do you plan to do so in the future? Thanks?

Nice Framework its help me lot. I am struggling to execute from Orchestrator. please assist me to execute from Orchestrator QUEUES and suggest me how to utilise this framework for Regression Test packs.

Is it possible to generate the logs in excel format rather than the notepad 

RPA Testing framework - Hi Stefan,
Thank you for the framework design , it is really good and very well scaled.
I have enhanced the test cases pickup functionality and modified it using excel sheet to select and drive the various test suite like SMOKE , Regression etc. and it worked like queue functionality.


Works very well - Thanks! This is just what I was looking for. Easy to set up and to execute 1 or many tests.


Security policy prevent installation of libraries - Sadly unable to proceed because security policies block the import of libraries. Can the required library be included into the UiPath installation? Incorporating TDD into testing framework as part of UiPath installation will help developers to create quality RPA bots. I will give 5 stars if required libraries add into UiPath installation and a sample PDD translated into unit tests.


Testing Framework for UiPath

Testing Framework for UiPath

Help

How To