Appium vs. FitNesse

Appium works well for well-structured mobile applications test automation that is particularly easy to leverage when different pages of the app use similar building blocks. If it takes time for some content in the app to be rendered, ask your dev team to add progress indicators and ensure they are accessible. That might be more complicated to do with Appium, though, if there's no good contact with Dev team established so you can request accessibility IDs added quickly enough when needed. Appium supports another locator strategies as well though (such as xPath or iOS class chain on iOS) but they wouldn't work as fast so you may get really slow tests.

Incentivized

Useful and straightforward. Appian and other low-code BCM tools can be easily integrated. Writing a script for a test is similar to writing a script in English. So simple to use because it's a wrapper class for selenium. FitNesse is being implemented with the goal of doing it correctly the first time. As a result, migrations of both the client and the server are made easier.

Incentivized

• Crossdevice: With Appium you can automate tests for Android and iOS both. There is no need to learn more than 1 language.
• Easy: It's really easy to configure and use appium; it's very useful when you're testing strategy is based on "developers write tests".
• Open Source: It's such a nice strength of appium, because you don't need to pay to use a good tool like Appium is.

Incentivized

• This program makes it simple to do both integration and acceptability testing.
• FitNesse was a huge asset to us when it came to rule testing.
• Scripting with command language is simple.

Incentivized

• There are a number of expected methods that are not implemented, yet. With a similar sounding name as Selenium with similar functions, people who are familiar with Selenium try to use methods that appear to be available, but give a "not yet implemented" exception when run.
• Documentation can be confusing.
• Setup was a difficult process. This may not necessarily be the case once you figure everything out, but the whole figuring it out process was difficult and I ran into many, many problems when I first started.

Incentivized

• Limitations with rich text fields.
• FitNesse cannot properly read the interface if labels or accessibility text is not available.
• Not used for Web interface testing.

Incentivized

I am rating 10/10 because Appium can use with multiple programming languages with multiple Test engines. Also, it works for both Android and iOS.

Incentivized

I would like to give 9/10 rating to Appium because of it can easily integrate with popular frameworks and CI/CD tools, as well as it is reliable, flexible and easy to use. The setup can bit complex in initial step, but once on configured it's very easy to use and enables stable and scalable mobile automation for real and cloud devices.

Incentivized

Most of mobile testing tools which are available in the market are paid license tools. But Appium is Open source mobile testing tool. We can create customised automation framework using Appium. It also supports various languages such as Java, Javascript etc. And also supports various operating systems such as Android, IOS etc. We can easily integrate Appium frameworks with CI/CD [Jenkins, Git etc].

Incentivized

The FitNesse testing automation framework is very simple to operate. It is simple to connect with the Jenkins and Bamboo environments. It is dependable, and it is simple and quick to include new tests. The process of debugging and fixing test failures is straightforward. FitNesse, including its installation, may be utilized with a minimum of fuss and difficulty. Maintaining scripts and monitoring their output is designed to be a relatively straightforward process.

Incentivized

• For cost of ownership, the increase is positive times infinity, as it's free to install and use
• Lead time for suite development can be a negative, if not planned for during sprint planning
• Using Appium to execute tests in parallel across a cloud solution can improve CI/CD cycles by 100's of a percent

Incentivized

• Saves developer time on regression testing.
• Developers can spend time on other prioritizes while FitNesse runs regression testing.
• Transitioning into another testing platform would be costly.

Incentivized