I agree that you don't need Selenium.
Instead of a Page Object Pattern, you want to model your request and response objects as classes. RestSharp has dependencies on JSON serializer and deserializer classes, so you set up things like Customer customer = response.Convert<CustomerResponseObject>();, and your object hold the object structure.
It seems you are trying to click on the disabled icon. Selenium does not click on the disabled button.
You can wait until the element gets enabled using WebDriverWait.
WebDriverWait wait = new WebDriverWait(driver, 15);
You seem good to go with some service testing.
NUnit -> I want to use parallel test methods execution/calling with Priorities using C# similar to TestNG in Java.
Both ideas are actually the same. Arrange is a Setup + Teardown.
Specflow -> Gherkin ...
Your first attempt would work if the button was not disabled.
Your other attempts are failing because <span> elements aren't clickable.
In a c#-ish pseudo-code, this would look something like this:
It looks like you are trying to click a disabled element. If the button was not disabled as it is seen in the first tag;
WebElement button = webDriver.findElements(new ByChained(
//You can replace  by ...
We had a similar problem with CodedUI. It does not run on a locked machine, some frameworks are like that.
We solved it in the following way:
Setup an remote Windows Server (Jumphost)
Setup another Windows Server (Test Runner)
Configure the Test Runner to not lock ever, never, ever.
Configure the Test Runner to be only accessible from the Jumphost and or ...
I don't think there is one universal approach to tool selection..
That is correct! I would like to explain which experience we made in our company.
Regarding the challenges:
Language: In our company we had e.g.business department, development center and e.g. some kind of testing centers for e.g. different departments. The problem is, that within the ...
I don't think there is one universal approach to tool selection, let alone to tool selection for test automation.
There are many areas and questions you need to consider before going for a particulat tool or set of tools:
How mature is the test tool? Is it available in a stable version, or is it still under heavy development?
How well can you use it? How ...
First, determine the business objective
In order to answer the questions about what to use, first determine the business objectives such as:
What speed is needed for deploying changes ?
What is the cost of automation, especially people ?
What is the future budget for Quality Assurance ?
How fragile is the application code ?
What is the revenue from ...
I think you are missing out the definition of "Framework"
A framework is comprised of a combination of practices and tools that are designed to help QA professionals test more efficiently.
These guidelines could include coding standards, test-data handling
You might be interested in JDI Light framework. This seems to be actively (more or less) maintained and evolved from former JDI that used to feature a lot of useful staff but is no longer supported as far as I understand.
TL;DR: There is no need for a framework at all. Using frameworks does not speed me up, just adds more complexity. Keep it simple!
Most of the "Frameworks" classes that I build are Domain specific. For example setup test users by code. Clean up environments before test-runs.
I dont like to call it a framework, that would make it bigger than it is. It is not ...
SonarQube also checks for security vulnerabilities (check beforehand if your application language is supported), see https://www.sonarqube.org/features/security/ .
You can define different rule-sets to scan a project
Users can mark issues as false-positives to discard them from future checks
It can be easily integrated into your CI tool
It has pre-defined ...
Make your tests independent of each other.
Jest has the concept of beforeEach and afterEach functions. Use these to start and quit your Appium session for each test.
When the app opens for each test it will be in the same place, and you can work forward from there.
It adds a little overhead to each test, but it will let you avoid major headaches trying ...
You can also wrap it in a function again to make it a bit more descriptive, and so you can include a sort of private methods.
If you are building and testing iOS apps someone within the project has to have a developer account, not? Just ask them for the xcodeOrgId and xcodeSigningId, as described in the documentation: http://appium.io/docs/en/drivers/ios-xcuitest-real-devices/
Not everyone (e.g. tester/devs) needs an account to run the tests, but you need atleast one person with ...