FitNesse vs. LambdaTest

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

One day, I needed to test a specific issue that was occurring only on Pixel phones. I turned to LambdaTest, quickly identified the problem, and was able to fix it. There hasn't been a situation where I felt LambdaTest didn't help, it's my go-to solution for testing, as it solves many problems.

Incentivized

• Easy to install.
• Command language is easy to create custom scripts.
• FitNesse tests are deterministic.

Incentivized

• Very accessible as multiple users can be added in each subscription
• Very reliable as it is very close to the actual device when it comes to operating system and version behavior
• There are a lot of options for devices and browsers that users can choose from when it comes to emulating and testing

• Logging can help any debug or error issues.
• A Java/Selenium developer is needed to maintain the FitNesse keyword library.
• Content.txt and properties.txted need to be added to the test suite in older versions to make it visible in a test run.

Incentivized

• More real devices should be added like I have Samsung mobile but it was not in the list
• It takes time in checking the link on LambdaTest if we compare with real mobiles
• Sometimes exact results are not matching as from real mobiles

The reason i have given the 10 points becasue the problem LambdaTest solves is providing access to all devices in one place, allowing developers to identify the same errors they would encounter on real devices. This makes life much easier, especially for developers who regularly face cross-device functionality issues. It's a big plus point that positions LambdaTest as an all-in-one solution.

Incentivized

Because of the ease of use of the platform, we just save a lot of time and effort with this as its a feature rich solution, we just need to upload app binary once and for everytime we need to test on a different device we can just directly install that binary on the device without the pain of reupload.

yes always available

Incentivized

haven't found any glitch while using this

Incentivized

The customer support team is very active and cooperative. Once, I contacted them in their off timings because of an issue, I got an instant reply from the executive and he resolved the issue very efficiently. This is why we have been using LambdaTest for more than two years. It is best suited for us.

Implementation of Lambdatest was very easy for different project requirements.

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

While BrowserStack is also a well-established platform, we found LambdaTest to offer similar and even better features at reasonable pricing. LambdaTest is more cost-effective than BrowserStack. LambdaTest provides a free forever plan, while BrowserStack does not. Even manual testing plans are better priced than BrowserStack’s. In terms of UI and onboarding, we found LambdaTest more user-friendly as well.

not all department, but we're using for our clients

Incentivized

• It does not necessitate any further setup or configuration.
• FitNess is an easy-to-use manual QA tool with a comprehensive report that aids stakeholders in better understanding the tested applications.
• Automated testing suites for a wide range of websites. In addition, it is quite beneficial for the ongoing maintenance of the test library.

Incentivized

• Automation testing has a bit of a learning curve
• Lack of real device keep that bug in your head if not on the website.
• Need to wait for a while for a new OS or browser version on the contrary of immediate availability in case of owning a lab