Protractor vs. XCTest

It is a strong fit for end-to-end acceptance and regression testing inside the browser.

Incentivized

It is very useful to add it mainly at the beginning of the app when each feature is finished and if the greatest importance of the app is its stability and a quick way to fix errors that are made during the changes. Do it when the app is finished; it's going to be quite time-consuming; however, applying it will go a long way in making sure the code hasn't been broken by changes and improvements.

Incentivized

• Async operations for browser-based validation tests. This kind of feature is a must-have for building tests to scale.

Incentivized

• Basic unit level testing of iOS apps/games and functionalities
• Xcode Test Recorder - mostly a feature for UI tests but as XCTest is related with XCUITest the UI recording is possible with Xcode environment.

Incentivized

• It would be great to see the Protractor API implemented successfully inside a non-Angular web application.

Incentivized

• Occasionally confusing
• Fails with automated builds without giving a good reason
• Not super flexible

Incentivized

Cypress.io is an alternative end-to-end test framework that does NOT use Selenium. Since I've only evaluated this tool as a possible solution, my estimation of its performance against Protractor is incomplete. However, if you and your team are looking for automation solutions outside of the Selenium scope, then Cypress.io may be a good fit given the problems you're trying to solve.

Incentivized

I haven't test any

Incentivized

• Increased the number of reliable end to end tests inside my test suites.
• Decreased the number and frequency of false-positive test runs/results.

Incentivized

• Faster way to know which issues appeared and fixed it.
• Easy way to install and teach to the programmers.
• More time invested on the project to implement.

Incentivized