TestProject Forum
Powered by leading experts in the test automation community

2020 New Features & Capabilities

We’ve had a great start to the first 2 quarters of 2020, and we plan to continue as always to release many more new cool features, integrations and capabilities!

So keep your feedback coming, as we are continuously building new features and improving according to your requests.

We are dedicated to developing with :heartpulse: the best platform for all of you to enjoy!

Recently Released

  1. TestProject Agents in Docker containers enabling to setup virtual labs & run tests in parallel
  2. Integration with Sauce Labs, BrowserStack & qTest
  3. Headless Chrome and Firefox browser support
  4. Enhanced API capabilities and brand-new Jenkins V2 plugin
  5. Detailed PDF reports with screenshots for all steps
  6. Intelligent Adaptive Wait mechanism leading to maximum test stability (within the recorder and SDK)
  7. New OpenSDK, including Python support making the entire development simple (Automatic reporting, drivers all setup for you and more!)

What’s Coming Up Soon?

  1. Recorder “makeover” including iFrame support with a cool new UI - You can test apps that were once very difficult to test (such as Salesforce, Wix, SAP, etc) super easily now!
  2. AI-based Self-healing capabilities for enhanced smart recorder
  3. New JavaScript SDK
  4. Support for iOS simulators
  5. TeamCity Integration
  6. Ability to share tests between accounts

And of course many more exciting features coming up in 2020! :star_struck:

5 Likes

Yessssss, this will be awesome.
Any chance there will be some ability to mark tests as flaky in job runs? I mean, I love the ability to isolate and just see failed steps/tests but it would be awesome to be able to mark a test flaky so that, as maintenance moves forward, certain tests wont have to be fixed or steps disabled until there is time to fix it within a project/sprint.

Hello @erick.caceres
With our new SDK, TestProject will be responsible for the scope of execution using the Runner class, and reporting using our Dashboards.
In case of flaky tests, this should be controlled over your version control environments like git, where you can mark flaky tests for example.

1 Like

Was hoping this was something that could be done in the web UI but that definitely is a good alternative.