Winium.Cruciatus | automated testing of Windows application

by 2gis C# Version: v2.10.0 License: MPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Winium.Cruciatus Summary

Winium.Cruciatus is a C# library. Winium.Cruciatus has no bugs, it has no vulnerabilities, it has a Weak Copyleft License and it has low support. You can download it from GitHub.

English description | Описание на русском.

Support

Quality

Security

License

Reuse

Support

Winium.Cruciatus has a low active ecosystem.

It has 138 star(s) with 66 fork(s). There are 33 watchers for this library.

It had no major release in the last 12 months.

There are 24 open issues and 8 have been closed. On average issues are closed in 57 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Winium.Cruciatus is v2.10.0

Quality

Winium.Cruciatus has 0 bugs and 0 code smells.

Security

Winium.Cruciatus has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Winium.Cruciatus code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Winium.Cruciatus is licensed under the MPL-2.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

Winium.Cruciatus releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Winium.Cruciatus

Get all kandi verified functions for this library.

Winium.Cruciatus Key Features

No Key Features are available at this moment for Winium.Cruciatus.

Winium.Cruciatus Examples and Code Snippets

No Code Snippets are available at this moment for Winium.Cruciatus.

Community Discussions

Trending Discussions on Winium.Cruciatus

Is Winium.Desktop required to be running even post development?

QUESTION

Is Winium.Desktop required to be running even post development?

Asked 2017-Nov-23 at 09:20

I am new to the Winium world. I tried playing with Winium.Cruciatus which seems to be working fine but not perfect. Hence, I am thinking to try Winium.Desktop.Driver.exe which I understand -

is a Selenium-compatible wrapper for Cruciatus, and
it is required to be running separately while development.

However, I wanted to understand that once the development is done and if the solution is deployed in production, will it (Winium.Desktop.Driver.exe) still be required to be running in advance for the solution to work?

My requirement: To automate the installation of a software on multiple VMs (domain joined) from one single VM.

If (yes)

{

I think it may block the installation if it requires explicit Admin permission to run. As we cannot go on each machine to click on 'Yes', which defeats the purpose of automation.
Because my environments will be Windows Server 2012 R2 and most of the time they are more restricted than a normal Windows like Win10.

}

If (no)

{

Any specific advantage of using Winium.Desktop.Driver vs only developing with Cruciatus library?

}

Note: Can someone of high reputation please create a new tag - 'Winium' as it seems this is required now as we already have few more questions on Winium.

...

ANSWER

Answered 2017-Nov-23 at 09:20

Winium.Desktop is a testing tool, it is usually used to automate end-to-end or other functional testing scenarios. When it is used as testing tool, then it is only required during development/testing phase, not in production.

But if you use Winium.Desktop not for testing, but as an automation tool, for example to automate installation of a software, i.e. Winium.Desktop is a core part of solution that runs setup program and clicks next or something, then you will need Winium.Desktop during deployment phase.

Key advantage of Winium.Desktop over Cruciatus is that it provides Selenium interface and works as client-server, which is useful for test automation, as client-server can be scaled, and Selenium interface is well known and there are a lot of tutorials on how to use it.

If you just need to automate installation of some software (i.e. do not need to do actual testing using Winium), I would suggest looking into direction of one of IT infrastructure automation tools like Ansible, Chef, etc.

Regarding admin rights I suggest to open an issues at https://github.com/2gis/Winium.Desktop/issues describing your use case, probably there is a way to run it without admin rights or grant access only once.

Source https://stackoverflow.com/questions/47420814

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Winium.Cruciatus

Add reference to Winium.Cruciatus in UI test project (install NuGet package). Create a map application. Use created map in tests. Run your tests and watch the magic happening.
Add reference to Winium.Cruciatus in UI test project (install NuGet package)
Create a map application
Use created map in tests
Run your tests and watch the magic happening
Add reference to Winium.Cruciatus in UI test project (install NuGet package).
Add reference to Winium.Cruciatus in UI test project (install NuGet package)
Create C# Console Application project and use this code: namespace ConsoleApplication { using System.Windows.Automation; using Winium.Cruciatus.Core; using Winium.Cruciatus.Extensions; public class Program { private static void Main(string[] args) { var calc = new Winium.Cruciatus.Application("C:/windows/system32/calc.exe"); calc.Start(); var winFinder = By.Name("Calculator").AndType(ControlType.Window); var win = Winium.Cruciatus.CruciatusFactory.Root.FindElement(winFinder); var menu = win.FindElementByUid("MenuBar").ToMenu(); menu.SelectItem("View$Scientific"); menu.SelectItem("View$History"); win.FindElementByUid("132").Click(); // 2 win.FindElementByUid("93").Click(); // + win.FindElementByUid("134").Click(); // 4 win.FindElementByUid("97").Click(); // ^ win.FindElementByUid("138").Click(); // 8 win.FindElementByUid("121").Click(); // = calc.Close(); } } }
Run ConsoleApplication and watch the magic happening

Support

Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug.Fork the repository to start making your changes to the master branch (or branch off of it).We recommend to write a test which shows that the bug was fixed or that the feature works as expected.Send a pull request and bug the maintainer until it gets merged and published. :smiley:

Find more information at: