Posts tagged with: jira


24.11.2014

New JIRA integration and Pivotal Tracker support

The latest release of Testlab has been added with a bunch of enhancements for integrations:

  • A new integration method (based on JIRA’s WebHooks) has been added. This brings us the support for JIRA OnDemand.
  • New JIRA integration method supports pushing JIRA’s issues as requirements / user stories to Testlab. This makes it possible to push stories from your JIRA Agile to Testlab for verification.
  • A brand new support has been added for Pivotal Tracker agile project management tool. You can now easily manage and track your project tasks in Pivotal Tracker and in the same time, test, verify and report your implementation in Testlab.

Read further for more details on these new exciting features.

 

Support for JIRA OnDemand

To this day, Testlab has supported JIRA integration with best in class 2-way strategy with a possibility to freely edit issues in both end systems. For this to work the JIRA has had to be installed with Testlab’s JIRA plugin, which provides the needed synchronization techniques. Atlassian’s cloud based offering, JIRA OnDemand, won’t allow us to install custom plugins which leads us to the situation that the 2-way synchronized integration possibility has been possible only with JIRA instances installed on customer’s own servers.

The new JIRA integration strategy has been implemented in a way, that it is possible to configure it in use by just using JIRA’s WebHooks. This requires no plugins and brings us the support for JIRA OnDemand instances. Keep in mind, that the new simpler integration strategy is also available for JIRA instances installed on your own servers.

 

One-way integration for JIRA’s issues and stories

The new integration method works in a way that issues and stories are created in JIRA and can be pushed to Testlab. This is possible for issues / bugs and also for requirements. For example, you can push stories from your JIRA Agile to Testlab as requirements which makes it possible to integrate the specification you end up designing in your JIRA as part of specification in your Testlab project which you aim to test.

You can read more about the different integration strategies for Atlassian JIRA here.

 

Configuring the integrations

integration_configuration

All new integrations, including the JIRA integration for issues and requirements and the Pivotal Tracker integration, are implemented in a way in which they can be taken in use by yourself. The project management view in Testlab has a new Integrations tab which allows you to configure the (Testlab side configuration) for these integrations. Integrations may also include some preliminary set up for them to work and instructions for these are provided in the plugin specific documentation.

 

 
Pivotal tracker integration

Pivotal Tracker is an agile project management tool for software team project management and collaboration. The tool allows you to plan and track your project using stories.

Your Testlab project can be integrated with Pivotal Tracker to export assets from Testlab to Pivotal Tracker as stories and, to push stories from Pivotal Tracker to Testlab’s project as requirements.

pivotalkuva

 
Importing Testlab assets to Pivotal Tracker

pivotal_import_testlabThe integration works in a two way manner. First, you have an option to import assets from your Testlab project to your Pivotal Project as stories to be tracked. You have an option to pull requirements, test runs, test sets, milestones, issues and even test cases from your Testlab project. When done so, a new story is created to your Pivotal Tracker project. It is as easy as dragging an asset to your project’s Icebox in Pivotal.

 

 
Pushing stories from Pivotal Tracker to Testlab

pivotal_importedYou also have an option to push stories from your Pivotal Tracker project to your Testlab project. This way, you can easily

  • push your stories from your Pivotal Tracker to Testlab project’s specification as user stories to be verified and
  • push bugs from your Tracker to Testlab project as issues.

Using Pivotal Tracker with Testlab is an excellent choice for project management. This way you can plan and track your project activities in Pivotal Tracker and in the same time, test, verify and report your implementation in Testlab. 

You can read more about setting up the Pivotal Tracker integration here.

 

To recap, the new features

  • bring you support for Pivotal Tracker, one of the best in industry agile project management tools,
  • add support for Atlassian JIRA integration where issues from JIRA are pushed to Testlab as issues and/or requirements and
  • add support for JIRA OnDemand.

We hope these new features make the use of Testlab more productive for all our existing and future clients.

 

 

 

Facebooktwitterlinkedinmail


Tags for this post: announce features integration jira pivotal tracker release screenshots 


24.1.2014

New feature release with importing and exporting

We are proud to announce a new major release of Testlab (Henrietta Lacks). This update brings you new major features such as importing and exporting data from spreadsheets, quick searching of assets in your project, enhancements to our plugins and many more!

 

video_organize_as_projects

 
Importing and exporting data

For easy adoption Testlab now offers import feature for your existing test cases, requirements or issues with a CSV format using office tools such as Microsoft Excel. Data from your projects can also be exported in identical format.

The feature supports importing requirements and their hierarchy, test categories, test cases including steps and issues. We also support importing values for custom fields, file attachments and comments.

video_adapts_to_your_process

 
Searching assets

Enjoy a fast and thorough searching function to find the assets you are interested in your project. Type in a keyword and you’ll get an organized result list for matching assets for easy access.

The search is implemented as an always accessible search field in your Testlab toolbar. The use of this field should be familiar for all users of some kind of embedded search, such as Mac’s Spotlight.

video_verify_track_and_report

 
Coverage enhancements

The coverage view is essential for knowing what has been tested for your application – how your design has been verified. We added some features for coverage reporting such as:

  • Filtering in features which have testing results in your project. This helps to filter out all the features from the view which you never intended to be tested in your version or a run you’re reporting against.
  • Content popups for related assets: By hovering your mouse on coverage related test cases and issues you’ll get instant popup describing the hovered asset.
  • Added “Not in test run” status as a reported state in results bar. This tells you if there are tests still to be scheduled for the feature.

 

video_manage_users

 
Drag and drop files

Attaching files to your assets in Testlab cannot get easier. You can now drag and drop files on your browser to automatically upload and attach them. You can even drop multiple files to upload them all at once (feature requires dropzone support and works currently in Chrome, Firefox, Safari 6+ and IE10+).

 

  

JIRA plugin enhancements

Our two-way JIRA plugin has been enhanced with the following features:

  • Issue types which are synchronized to Testlab can be now chosen. This way you can for example synchronize only defects and leave new features unsynchronized.
  • The fields which are not automatically mapped to Testlab’s fields can now be configured to be mapped to Testlab’s custom fields. This way you can synchronize custom field content or synchronize a missing JIRA field (such as estimate) to a custom field of your choice in Testlab.

 

Session management UI

Testlab now offers an user interface for administrators for which they can see all active Testlab sessions. This way they can transparently see how many licenses are in use and optionally terminate sessions from their Testlab.

 

Other enhancements

In addition to the above, the version features numerous other enhancements. Some of most notable include:

  • Jenkins plugin class level mapping: Test cases in Testlab can now be mapped to Jenkins’ run tests at parent level. For example, mapping a test case with “com.example.tests.ui” in Testlab will be set as failed if any tests in Jenkins with identifier starting with “com.example.tests.ui” fail.
  • Reordering test case steps: Steps of a test case can be now reordered by dragging and dropping.
  • Adding issues for test run’s test cases: A new icon button has been added to test runs panel which allows you easily add a new issue for a test case in an existing test run. For example, this way you can add issues later on to the test run if some are missed during the execution.
  • More quick links: The user interface now contains more quick links between assets. For example test run panel’s “Added issues” counts can be clicked to open up the related assets in a popup window.
  • Requirement class icons: Different requirement classes (user stories, use cases etc) now feature different icons. This way the different types of requirements are easily distinguishable in the user interface.
  • Rich text editor tab / de-tab: Pressing tab or shift+tab in rich text editor now indents and outdents text for easier editing.
  • Better keyboard navigation: Keyboard navigation in the user interface is now better, especially in the hierarchy trees.
  • Opening attachments inline: Attached files with browser supported content types are now opened inline directly in the browser window instead of forcing the document to be saved to disk.

 

Sincerely yours,

Meliora team


henrietta_lacksHenrietta Lacks (1920 – 1951) was an African-American woman who passed away of cervical cancer in 1951. Little did she know that her fatal tumors would hold a key to numerous medical advancements (polio vaccines and chemotherapy for example). Her biopsied cells were found to really thrive outside her body and would be used to create the first immortal cell line for medical research so that her cells are still alive today – over 60 years after her passing. Her cells were used to create the so called HeLa cell line for scientific research – currently the oldest and most commonly used human cell line. They were also the first human cells successfully cloned in 1955.

Henrietta’s cells have been mailed to scientists around the globe for research and scientists have grown some 20 tons of cells. Henrietta is still living today, around the globe and bigger than ever. Find out more by listening Radiolab’s great short story about the subject!

 

Facebooktwitterlinkedinmail


Tags for this post: announce features jenkins jira release video 


26.4.2013

New version of Testlab released [Pitch drop]

Meliora is pleased to announce an update for Meliora Testlab codenamed “Pitch drop”. This version brings you a number of enhancements and optimizations and is available immediately for our hosted version customers. The version includes many features requested by our clients and we would like to thank you for all the feedback!

Jira integration

The version offers features for integrating your Testlab with Atlassian Jira issue tracker. Implementation includes a true two-way synchronization module which enables you to synchronize the issues in real time between your Testlab and Jira deployments. This way you can continue to use your established method of working with issues with Jira and be more productive with requirement and test case planning and test execution with Testlab.

This feature is available for all Enterprise Suite installations. You can read more about the feature from here.

 

Real time project events

To keep you up to date with events in the project you are currently logged in Testlab delivers you real time events. The events are presented as floating notifications at top right corner of the user interface. Clicking the notification opens up the associated asset in your Testlab.

In addition to the regular project events such as changes in the project assets all assignments are delivered as sticky notifications. This means that when an asset is assigned for you the notification will stick to your user interface as long as you click the notification to open up the asset or dismiss the notification.

 

Notice board

A new dashboard widget is offered to easily communicate with the users in your testing project.

A project notice board offers a place to store your shared project assets and publish announcements. Announcements can be targeted to specific user roles and optionally tagged as important which delivers the announcement to all users on next login in a pop up window. By default test managers and project managers can manage the content of project’s notice board but new permission keys are included to control who can publish the content. In addition to this all administrator users of your company can publish company wide announcements which are shown to users in all projects in your company.

 

Easier re-testing

Testlab’s test case hierarchy tree is enhanced with a new set of filters which make it easier to highlight the test cases for re-testing.

Filters make it easy to pick all not passed test cases from current test case hierarchy as a whole, for a specific version or for a single test run. When re-testing previously tested features use these filters in execution planning view to easily add test runs for test cases previously failed, blocked or not tested.

Combine the above with the use of your personal work set in execution planning and adding test runs for re-testing couldn’t be easier!

 

Streamlined issue editing

Editing window for issues has a new streamlined layout which makes commenting of issues easier.

 

Commenting enhancements

When publishing comments the content is now automatically linkified so that all external links are rendered as clickable links. In addition to this comments can now be deleted.

 

Performance improvements

In addition to the features described above Pitch drop includes some magic under the hood to make the use of Testlab even snappier than before with network transport enhancements and more intelligent on-need-basis refresh logic for asset hierarchies.

Sincerely yours,

Meliora team


Pitch drop? In 1927 Professor Parnell heated a sample of pitch and poured it into a glass funnel with a sealed stem. Three years were allowed for the pitch to settle, and in 1930 the sealed stem was cut. From that date on the pitch has slowly dripped out of the funnel – so slowly that now, 80 years later, the ninth drop is only just forming. In the 80 years that the pitch has been dripping no-one has ever seen the drop fall. You can try your luck here.

Facebooktwitterlinkedinmail


Tags for this post: features jira product release 


28.3.2013

Testlab integrates with Atlassian Jira

We are happy to announce an integration module for integrating your Testlab with Atlassian Jira issue tracker. We’ve been working hard to bring you a true two-way synchronization module which enables you to synchronize the issues in real time between your Testlab and Jira deployments.

Advantages

Simple: this module enables you to seamlessly integrate Jira issues with Testlab’s test cases and other test management data. If your organization already has an established method for working with issues, with this plugin you can continue to handle issues like you are used to *and* be more productive with test case planning and test execution with Testlab!

How it works

The module is implemented as a plugin at Jira side and as an integration interface for the plugin at Testlab side. The following diagram describes the synchronization principle at high level.

Both peers have an event listener which publishes the changes in issues in real time. This means that when an issue is updated, commented or a file is attached to it in Jira the change is immediately pushed to Testlab and vice versa. As said, we currently sync issue details, comments and attached files.

In addition to real time push a scheduled (every 15 minutes) synchronization job is triggered. This means that Jira pushes all issue updates from the last synchronization point of time to Testlab. Testlab processes the data and replies with a push of it’s issue changes in similar fashion. This allows us to synchronize the issues between the systems even if the real time push fails for some reason for example due to network problems. We allow you to choose a conflict resolution strategy when overlapping updates occur to always honor the latest data, the Jira data or Testlab’s data.

The actual data between Jira and Testlab is pushed through a secured and key authenticated network channel. Just make sure your Jira allows secured HTTPS to make the push from Testlab to Jira secure.

Great! How do I get it?

The integration module is available to all our enterprise suite customers.

Facebooktwitterlinkedinmail


Tags for this post: announce features jira plugin product 


 
 
Best-of-class cross-browser hosted SaaS quality and test management, testing and issue management tools to improve your quality. Site information.