Release notes v0.7.0


#1

This release introduces several new features expanding on existing features and introducing new ones. As with a previous version the Drag-to-Code workflow has been introduced and so far turned out to be much more efficient, we’re rebuilding the Page Object panel to act as a Page Object Class Overview.

Never heard about the Drag-to-Code and Snippet oriented workflow? It’s maybe time to revisit our Getting Started introduction, which you can start via the App Menu (Help -> Getting Started) to get a glimpse of the new workflow supports. We’re certain this will boost your productivity even more.

Important
Since the project templates changed for proper Jira support, please make sure to restore templates, which will copy them over to your global user folder.

As always, the whole Webtestit team is looking forward to your feedback.

Reporting:

  • We now do support persisted Reports. That means even though your projects setup, like Endpoints etc. change, you can still open an existing report file and get all the details. This allows to archive reports and take a look at them at a later time plus enables easier viewing of reports generated by a CI environment.
  • Oh and btw you can now also quickly run only the failed tests directly from within the Report

IDE features:

  • New page object overview. With this change the functionality to create Page Objects by drag and drop to the Page Object panel was disabled and instead changed to act as a Page Object Method Overview. The idea is to further promote the Drag-to-Code feature and usage of EditorSnippets. It turned out that the previous approach just wasn’t satisfying our UX demands as much as needed. Right-clicking methods in the Page Object Overview will now allow you to jump directly to the proper location in the code. This also works for the element panel.
  • Support for Selenium Grid. An often stated request by the beta users was to support the execution on a local Selenium Grid environment. With this update you can now configure those endpoints, pretty much the same way like SauceLabs endpoints.
  • Various UI improvements: Amongst these is the more native frameless app layout for Mac users and new out-of-sync states in the page object and elements panel. Browsers that now need manual configuration will have a help indicator in the Endpoint panel.
  • If the LogPanel shows an issue with a file, like a stacktrace information, you can now CtrlCmd+Click it and directly navigate to the mentioned file.
  • We now do support EditorConfig files. Click here to learn more about that standard. New projects will come with a default setting created.
  • You can now run either all or the active test file directly from within the Endpoints panel
  • Various bug fixes for the CLI, like proper shutdowns for unused browsers after test runs.

TypeScript:

  • Automatic npm installs when executing tests on a TS project. This way you can get your project up and ready for execution even though you e.g. freshly checked it out of your Versioning system or downloaded our sample project.
  • We’re now cleaning the dist folder on every new test execution in order to get rid of any build artefacts from the previous run. These changes are effective only with new TypeScript/Protractor projects.
  • Various bug fixes

You should receive the new version automatically via the auto-updater once you restart the app.
Alternatively, you can download the latest version here


listed #2

pinned globally #3