Think you’ll be pleasantly surprised how powerful TestProject is.
I’ve a months+ experience with TP (we decided to use it as our chosen framework, after evaluated several others, including Functionize, Mabl, TestCafé Studio & Cypress) - and find it to be a really capable framework. And just keeps getting better (with AI, expanding SDK support, and upcoming Git support for recorded tests).
In regards to your questions:
- Tests are run on your own hardware using agents (which make handling selenium and appium drivers a cake-walk). You can deploy as many agents as you want, either as a locally installed executables or via Docker.
It is also possible to forego agents, and run tests using BrowserStack / SauceLabs if you’re willing to pay for testruns in their cloud-based infrastructure.
- Git integration is supported for tests that are exported to, or created with, an SDK. If you’re looking to leverage recorded tests, currently Git support is only for exported tests. There is no way (yet) to record a test, export it, and then re-import it (f.ex. to use the recorder to maintain the test) - but this feature is slated to be released in Feb 2021.
- TestProject tests run quickly (at least the web-based one’s I’ve created)! They’re basically just selenium tests and run just about as quickly (only caveat is when using plugins - I notice that test steps using certain plugins can take a bit longer - but we’re talking about fractions of a second here, so not a deal breaker). I don’t have any experience with Appium (Android / iOS) test yet - but other forum members can certainly provide more info as to that.
Some key features: (very subjective - YMMV)
Element Library: Recorded tests build up a library of elements. When used prudently, this can allow an element used in many tests to be maintainable from a single object.
Recorder: The recorder is one of the better recorders I have tried - and allows you to debug tests “on the fly”. It also has useful tools for interacting with and exploring elements in the application under test.
Plugins: There are many useful plugins to choose from. There is also support for creating your own plugins.
Parameters: Easy to setup test parameters (per test and also shared for a whole project).
Nested tests: A test can consume another test (which itself can also include other nested tests)
Reports: The reports generated for tests are really nice. Easy to use and pretty informative
SDK: Test-Project has good SDK support. Java, C# & Python are supported (other languages are also underway).
Live Support: The level of support offered for a “Free Test Platform” is commendable. When necessary, support techs have helped me directly on-line (via Zoom). Kudos to them for this!
As to negatives (also fairly subjective)
Issues you may experience with TestProject are rather dependent on what your needs are. The main niggle I have with TestProject is this:
Documentation: There are lots of guides, but many are incomplete (some even out-dated). While amazingly simple to get started with, there are certain features that are not so intuitive. Documentation is pretty basic, and some features are poorly documented, if at all. The documentation also lags feature releases somewhat. If you’re gonna use TestProject, be prepared to dive into the Forum, and to use their Live Support. The community is an important part of the experience.