Testing Framework for UiPath

Hi Stefan, 

I downloaded your latest version of the above testing framework. so, while executing i am getting error regarding "Get test locations ui " activity which is under package TestingFrameworkUI  v1.3.3 . Earlier the same file was working fine till last week but from yesterday we are unable to run this file due to the below error 

Error details is as follows:

Source: Get test locations ui

Message: Could not load file or assembly 'WPFUI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

Exception Type: System.IO.FileNotFoundException

RemoteException wrapping System.IO.FileNotFoundException: Could not load file or assembly 'WPFUI, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. 

   at TestingFrameworkUi.GetTestLocationsUi.OpenSelectTestsWindow(String rootFolderPath, String projectName, SortedDictionary`2 testRunInformation, Dictionary`2 expandedItems, Dictionary`2 windowInformation)

   at TestingFrameworkUi.GetTestLocationsUi.Execute(CodeActivityContext context)

   at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)

   at System.Activities.ActivityInstance.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at UiPath.Executor.BaseRunner.EndExecute(IAsyncResult result)

   at UiPath.Executor.InProcessRunner.EndExecute(IAsyncResult result)

   at UiPath.Core.Activities.InvokeWorkflowFile.EndExecute(AsyncCodeActivityContext context, IAsyncResult result)

   at System.Activities.AsyncCodeActivity.System.Activities.IAsyncCodeActivity.FinishExecution(AsyncCodeActivityContext context, IAsyncResult result)

   at System.Activities.AsyncCodeActivity.CompleteAsyncCodeActivityData.CompleteAsyncCodeActivityWorkItem.Execute(ActivityExecutor executor, BookmarkManager bookmarkManager)

My Studio version is studio 2020.10.2 enterprise edition however its working in community version of studio 2020.10.6

Thanks in advance for your response.

Hi Stefan,

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

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.

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.

Hi there,

Is this project actively maintained do you plan to do so in the future?

Thanks?

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 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.com

Thank you

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.

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.