Release 2.0

Release 2.0 brings quite a few, new exciting features to accelQ platform along with improvements in overall system stability. Here is a brief listing of important enhancements in 2.0.

1. Context Refactoring

This comprehensive new feature allows the user to refactor assets belonging to a Context including Views and Actions. You can now move around Actions freely between different Contexts, giving you an ability to make structural changes. It also brings in an ability to change the "Owner Context" of an Action. All the dependency calculations are computed and verified before the operation is committed.

You can access this feature from the following entry points:

1. In the Context home page, with a top toolbar action item, "Refactor"
2. In the Action logic sidebar while trying to edit the Owner or Origin context

Click here for a detailed article on this feature.

2. Support for verbose mode for reporting

Your test report is now capable of reporting extensive/detailed messaging related to test run. By default, the test report is opened in "standard" mode and you can switch to "verbose" mode by clicking the action icon in the test case detail header.

3. Defining user roles

Your Tenant Admin can now define multiple user roles with a granular control on access to various entities. When a user is added to a Project, an Admin can assign specific role to a user. Same user can be assigned different roles in different projects. This feature allows fine grained control on managing access to entities and there by preventing unintended updates to test assets.

Click here for a detailed article on this feature.

4. Restricting access to an Action from a Scenario

An action can now be marked to be visible or not visible from a Scenario. By default, the visibility is set to "on". In some instances, when the Action is implemented purely for modularity purpose (to be used in another Action) and you do not want this Action to be exposed at the Scenario level, turn this indicator "off" in the Action sidebar. This allows you to filter some of the noise, which otherwise could cause confusion while building a Scenario.

Click here for a detailed article on this feature.

5. Filters on navigation grids

You can now build comprehensive filters on all the entity grids in Navigator. You can combine filters based on multiple meta fields. In addition, you can also search a grid based on the name of the entity. Any filter that you setup is persisted at a user level, so that the next time user visits the grid, appropriate filter is automatically applied.

Click here for a detailed article on this feature.

6. Native support for Bamboo CI integration

A native plugin is now available for initiating accelQ test execution as a functional validation step from Bamboo. You can embed automated sanity test as part of your regular CI build process so that a functional validation is achieved as part of continuous builds.

Click here for a detailed article on this feature.

7. Native TFS integration for requirements and bug tracking

You can define integration points in accelQ for Requirements and Defect tracking managed on TFS platform. You can trace accelQ Scenarios with TFS User Stories and also, (auto) create defects from test reports, against TFS integration point.

Click here for a detailed article on this feature.

8. Extended parameterization options for API wizard

When you are inserting API verification via the wizard mode, you are now presented with a full set of parameterization options for both request creation and response validation. You can parameterize the request URL, request headers and node values in the payload. Similarly, you can use Action or Global parameters for expected values in the response. This makes possible, chaining of multiple API calls or UI to API interactions in a single step.

9. Icon refresh

All the icons in the system are refreshed with newer and light-weight, flat versions of images. Icon rendering is re-engineered, so now you won't experience the flicker that sometime may occur when you hover on an icon. 

10. Bug fixes and performance improvements

• Thread safety with parallel test execution for API and other back-end testing
• Pagination of navigation grids so that content is loaded faster.
• Conditional statement related stability items.
• Loop Statement improvement in parameterization.
• General bug fixes and stability related work items.
• Other performance improvements.