Posts tagged with: screenshots


28.9.2018

Testlab – Circleville release

We’ve released a new version of Meliora Testlab – Circleville. Please read more about the new features and changes in this release below.

 

Restricting the visibility of assets
Choosing fields to be reported

In Circleville, when rendering reports, you have an option to choose the fields you wish to include on your report. This applies to most reports which feature a table or listing of some kind. In previous versions, the report templates included listings with a pre-defined set of fields present.

When choosing the fields you also have an option to arrange the fields to the order desired. The fields and the corresponding order of them are saved as you configure your report.

 

Configurable requirement classes

You now have an option to configure your own classes for requirements, if needed. When you configure one, you enter a title and choose an icon for it. This information is used to present the requirements in the UI. The classes can also be used in reporting.

By using customized classes you have an option to choose the custom fields which are specific to each class. See below.

 

Different custom fields for different types of assets

When configuring custom fields you now have an option to choose which type of issue or which class of requirement the field applies to. This way, for example for issues, you can have a different set of fields for “defects” and different set of fields for “new features”. As said above, this applies to different classes of requirements too.

 

Help manual with inbuilt search

The help manual incorporated to Testlab now has a searching function inbuilt. Searching the manual is easy: Just enter a search term to the field in the lower left-hand corner. The contents index of the manual gets highlighted for pages with hits and in addition, the current help page open gets highlighted with yellow for any possible hits.

 

In addition to the above
  • Workflow changes: Deprecated assets such as deprecated requirements or test cases cannot be edited anymore. To edit them, use appropriate action to transfer the deprecated assets back to design.
  • Workflow changes: By default, closed issues cannot be edited anymore. To edit closed issues a new permission “defect.edit.closed” must be granted to the user.
  • When test cases in a test set of Planning view are hovered on, the details of test cases are presented in a tooltip.
  • Table views of requirements and test cases now show the number of assets presented.
  • Links to open issues in Testlab can now be formatted to include the issue ID instead of the primary key.
  • Reporting: “List of issues” and “Issue grouping” report templates now support a new field “Requirements” which allows you to report the requirements linked to the issues via the test cases the issues are linked with.

 

Thanking you for all your feedback,

Meliora team


Canis Majoris

A small town in Ohio US, Circleville, is best-known today as the host of the Circleville Pumpkin Show held to celebrate local agriculture since 1903. This picturesque town has a sinister history of its own, though.

A mystery still unsolved spans from sometime in 1976 to late 90s when local residents started receiving personal and threatening letters with details of their personal life included. Thousands of these letters, called Circleville Letters, were sent to citizens and local city officials. The letters were written in block letters and were sent by an anonymous sender.

Finally, a man thought to be responsible for the letters was apprehended on a case related to few recipients of these letters. He was found guilty for an attempted murder and sentenced for years in prison. 

The letters kept on coming, though. The officials put the man under solitary confinement which did not stop the letters and they were certain that this man could not be sending the letters. A lot later, even a team of television producers working on a television document received one. The letters kept on coming till the late 90s and suddenly stopped. 

(Source: Gizmodo, Reddit, photo by Aaron Burden)

Facebooktwitterlinkedinmail


Tags for this post: announce features product release screenshots 


9.7.2018

Testlab – Globster release

We’ve released a new version of Meliora Testlab – Globster. Please read more about the new features and changes in this release below.

 

Restricting the visibility of assets
Restricting the visibility of assets

Your projects can now be specified with rules which restrict the visibility of certain assets in your project. This can be applied for requirements, test cases and issues and applied against their workflow status or values in customized fields.

For an example: If you have a 3rd party users in your project for which you’d wish to hide a set of requirements in your project, you can define a rule which limits the visibility of these requirements only to your own users in a certain user role.

 

Restricting the visibility of customized fields

Similarly to the assets, for all custom fields, it is now possible to choose the user roles for which the fields are visible for. This makes it possible to hide some information from your assets from a certain group of users.

When the field is restricted for certain roles, only users in these roles have access to the information in this field. Please refer to the help manual of Testlab for more details on how the data is visible and/or hidden.

 

Rich-text custom field type

A new type of custom field has been added which enables you to add a field with long richly formatted text for your assets. This new type of field differs in logic from other custom fields in a way that all rich-text typed custom fields are always presented on a separate tabin the design view.

 

More custom fields

The maximum number of custom fiels per asset type has been increased from 10 to 150.

 

Updates to plugins

Jenkins-, Confluence-, and JIRA-plugins have been released with bugs fixed and minor enhancements. Please update accordingly.

 

In addition to the above
  • Run Tests in … option in test case menu now has a filtering picker for picking the test run the tests should be executed in.
  • Selecting a report to be viewed is now easier in the UI as the listing of reports is now configurable and easier to filter.
  • With Execution history tab in Test design view it is now possible to inspect combined execution history for all test case’s revisions.
  • Reports can now be generated also in Finnish language.

 

Thanking you for all your feedback,

Meliora team


Canis Majoris

A globster is an unidentified organic mass that washes up on the shoreline of an ocean or other body of water. The term was first coined by Ivan T. Sanderson for the so called Tasmanian carcass found in 1960.

Globsters may present such a puzzling appearance that their nature remains controversial even after being officially identified by scientists. Some globsters lack bones or other recognisable structures, while others may have bones, tentacles, flippers, eyes, or other features that can help narrow down the possible species. The picture on the right is the “St. Augustine Monster” that washed ashore near St. Augustine, Florida, in 1896. It was first said to be the remains of a gigantic octopus but in 1995 analysis it was concluded that the globster in question was a large mass of collagenous matrix of whale blubber, likely from a sperm whale. 

(Source: Wikipedia)

Facebooktwitterlinkedinmail


Tags for this post: announce features plugin product release screenshots 


13.4.2018

Testlab – Canis Majoris release

We’ve released a new version of Meliora Testlab – Canis Majoris. This version includes major additions to the REST interfaces of Testlab and several UI related enhancements. Please read more about the changes below.

 

REST API enhancements
REST API enhancements

The REST based integration API of Testlab has been enhanced with a number of new supported operations. With Canis Majoris, it is possible to add, update and remove

  • requirements,
  • test categories,
  • test cases and
  • issues.

Add operation maps to HTTP’s POST-method, update operation maps to PUT-method (and in addition, supports partial updates) and remove operation maps to DELETE-method. More thorough documentation for these operations can be found in your Testlab instance via the interactive API documentation (/api).

 

Test categories with fields

In previous versions of Testlab, test cases were categorized to simple folders with a name. In Canis Majoris, test categories have been enhanced to be full assets with

  • a rich-text description,
  • time stamps to track creation and updates,
  • a change history and
  • a possibility add comments on them.

 

In addition to the above
  • Date and time formats are now handled more gracefully in the user interface by respecting the browser sent locale.
  • Test cases of a requirement can now be easily executed by choosing “Run tests…” from
    • the tree of requirements or
    • from the table view of requirements.
  • Similarly, the test cases linked to a requirement can be easily added to a your work (test) set by choosing “Add to work set” from the table view of requirements.
  • Test case listing -report renders execution steps in an easy-to-read table.

 

Thanking you for all your feedback,

Meliora team


Canis Majoris

VY Canis Majoris (VY CMa) is one of the largest stars detected so far and is located 3900 light-years from Earth. The estimates on it’s size vary, but it is estimated to be 1400 to 2200 solar radii (distance from center of Sun to it’s photosphere).

The size of this object is difficult to comprehend. It would take 1100 years travelling in jet aircraft at 900km/hr to circle it once. Also, It would take over 7 000 000 000 (7 Billion) Suns or 7 000 000 000 000 000 (7 Quadrillion) Earths to fill VY Canis Majoris. There are also few videos on YouTube which try to explain the size for you. 

(Source: Wikipedia, A Sidewalk Astronomer blog)

Facebooktwitterlinkedinmail


Tags for this post: announce features integration product release screenshots 


5.3.2018

How to: Migrate from TestLink to Meliora Testlab

transSome of our customers have moved from using TestLink to our tool, Meliora Testlab. We’ve been asked to make this transition easier and so we decided to document this migration path, and this  post here describes how the migration works. Basically the migration moves your important test data from TestLink to Testlab so you can continue to work in your new tool.

 

When changing the tool, do I need to change the way I work?

This is a tough subject that deserves another post completely dedicated to that matter. To put it shortly, Testlab offers a lot of features that allow working in new ways, but most of the Testlink features are also in Testlab, so if there is no need to alter your way of working, you can do most of your work in the same way as before. TestLink’s “Test specification” view’s data can be seen in Testlab in “Test case design”. Assigning test cases to be tested in the simple form in Testlab is done by picking the cases to work set and then creating a test run, which tells the what release / version is being tested. Test execution is again pretty much the same again.

In nutshell – how does this all work?

In TestLink there is an export feature that allows you to export your test case data as XML. We can transform this data in to a format that can be directly put in in to the Testlab. When custom fields have been used in Testlink, the tool needs to be instructed how the custom fields are mapped in to Testlab fields. After the definition, a click of a button transform the data in to desired format.

For your convenience, Meliora will do this transformation free of charge (*). For our On-premise customers we can also deliver the tool to allow doing the transformation yourself.

The migration has five distinct steps:

  1. Modifying the Testlab to used format. ( optional )
  2. Exporting Test cases from TestLink testsuites.
  3. Describing the data mappings ( optional )
  4. Transforming the TestLink Export XML to csv format that Testlab can read
  5. Importing the test case data from csv.

The techical part behind these steps is pretty straightforward. Once you know how you want to migrate the data, the export-import will be just a few clicks for you.

*) Meliora reserves rights to decline of the free service on cases where making the transformation would engage Meliora with exeptional workload. This could happen if you would have huge amount of projects to be migrated.

 

What do I need to do before the migration?

Well, the only required thing is becoming a Meliora customer. Any edition of Testlab will do. A very very recommended thing to do is to plan how do you want to test with Testlab in the future. As Testlab offers many features that make testing easier that are not present in Testlink, it might be wise to change the way how testing is done at the same time when the tool is being changed. For example testlab has automatic revisioning, history, built-in (optional) review etc. so you might have made customizations to TestLink for these issues. These customizations are probably not needed anymore, so you need to decide if it is better just to ditch the customizations or do you want to continue using them. If you are in a hurry, fear not! Then you can just import all custom data and ditch the unneeded later.

 

General considerations

Most important thing to ensure is that your company’s testing work is not interrupted more than it has to. When you switch the tool, it is not effective if you continue using the old tool ( in migrated projects ) as you would be getting test case updates in two tools and test results in two tools for same project. Thus it is best to decide a timeslot for the switch and ensure everything goes smoothly when the time comes.

It is best to contact Meliora as you plan the migration and prepare a timeslot in case you want to keep to switch time in absolute minimum. Just create a support ticket and Meliora will help you getting the migration done smoothly.

Migration steps

 

Modifying the Testlab

Testlab, by default, has different fields and field Values than TestLink. You can, if you want, do the migration without modifying Testlab. Then the fields are going to be mapped by default. In case you decide to do the modification, these are the things to consider:

Choosing / Modifying a workflow

workflow-editIn testlab, the way how statuses are used are controlled by workflows. Workflows allow logic behind changing statuses – what statuses can be reached from what status, what fields are mandatory in which state and who has privileges to make changes. Testlab comes with two default workflows, called “simple” and “review”. The difference for test cases here is that review has a phase for review, where simple skips this. Basically you need to decide what statuses you wish to see in Testlab. The default Status transformations are depicted in following table:

 

 

 

 

 

TestLink Status
Testlab Simple workflow
Testlab With review workflow
Draft In design In design
Ready for review Ready for review In design
Review in progress Ready for review In design
Rework In design In design
Obsolete Deprecated Deprecated
Future Ready Ready
Final Ready Ready

You can add additional data transformations for the migration in addition to simply changing statuses. For example the “Testlab way” for handling test cases that are not yet runnable, is using a “Milestone” field to define when the test case is planned to be used. More on this on chapter “Describing the data mappings”.

Modifying the Testlab project

In case you have used custom fields and wish to keep the data in the custom fields in the future as well, you need to configure your Testlab’s project to include those. You’ll find the instructions for that in Testlab’s manual – it’s very simple operation.

Keep in mind, that you also have an option to import data from custom fields to description field. This makes sense when you do not want to lose this information, but you do not need to filter data in reports using custom field data.

If you are migrating data to multiple Testlab projects you can do the common modifications once and then copy the project with modifications. This way you do not need to do the modifications for all the projects separately.

 

Exporting test cases from TestLinkTestlink export options

In Testlink, you need to export test cases as XML for each project you wish to migrate.

  • In Testlink, go to “Test specification”
  • Choose “Actions” -> Export All Test Suites
  • make sure you have at least four boxes checked
  • Save your XML export file

 

Describing the data mapping

Before the transforming the data you can define how the TestLink data is to be transformed in the migration. Our on-premise customers that wish to do the transformation themselces do not need to do this as they are going to put this data in to tool themselves. Send the following information  to Meliora:

  • What custom fields are to be migrated. For each field describe to what field you want to import the data in to.
    • Example1 ) TestLink custom field “risk” values to Testlab field “risk”
    • Example 2) TestLink custom field “legacy link” added to the end of “description” field
  • How you want to change the data values
    • Example 1) TestLink custom field “risk” value “petty” to be “Low” in Testlab
    • Example 2) TestLink status “Future” to Testlab status “In design” + Milestone to value “Future”
Transforming the XML to Testlab csv

Here you have a few options:

  1. For SaaS users you can just send the XML to Meliora, and Meliora will do the transformation and import the data to your Testlab project. Just wait for the confirmation and you can start using your Testlab with imported data!
  2. For On-premise / SaaS users that want Meliora to just do the transformation, send the XML to Meliora and Meliora will deliver you an CSV that is ready to be imported in to testlab.
  3. For On-Premise users that want to do the transformation themselves, contact Meliora for details. Meliora will deliver you the tool along with instructions to do the transformation.
Importing the data from csv

The import itself is just a few click really:

  1. From Testlab menu choose Import -> Test cases
  2. Choose the csv file
  3. Try the import first with “dry run” option on. This will show errors / warnings should there be any. Here you will see if, for example, if you do not have a custom field in this project where you try to input data with the csv file.
  4. After you are satisfied with dry run results, uncheck the dry run box to really load the data in to the Testlab.
  5. Refresh the test case tree and start using your Testlab.

Final words

This document describes the basic setup of the migration process. As with all project more complicated than Hello World!, there will be unknown factors. You might have in-house customization done to your TestLink or you might want to include data from completely another source. Fear Not! Meliora can work with migrations that does not follow the ordinary path. Just contact our great support and we will work trough the migration together!

Meliora team

 

Facebooktwitterlinkedinmail


Tags for this post: announce features product release reporting screenshots 


26.1.2018

Testlab – Helios release

A new version of Meliora Testlab – Helios – has been released. In this version, one of the goals was to optimize the speed of the user interface which makes this version of Testlab faster than ever. Please read more about the changes below.

 

Faster UI

Several enhancements have been made to optimize the UI, rendering and backend services. Some are workarounds to browser-related bugs, some are different rendering strategies and some are optimizations in situations where there are lots of assets in your project. 

We hope these changes make the use of Testlab snappier than ever. As the changes are browser-specific and may benefit some users more depending on the configuration of the workstation, we are more than happy to receive any feedback from you on your experiences.

 

Comments for test results
File attachments for steps of test cases

Previously, one could attach files to test cases. In Helios, you can also attach files to individual steps of the test case. The editor for editing steps has a new configurable column available for which you can attach any files relevant to the specific step.

The files are presented to the tester when the test case is in testing. The files are also included to reports and to e-mail messages sent for the test cases if preferred.

 

Expand attached images to listing reports

Requirements, test cases, and issues in Testlab can be attached with files. These files might be images, which is most common in case of issues where images such as screenshots are used to describe the issues encountered.

In Helios, the detailed listing reports (List of requirements, List of test cases and List of issues) have a new option to expand the attached images. This way, when the report is rendered, the images are expanded and shown in the printed report.

And there is more

In addition to the changes above:

  • SAML-authentication can be used to authenticate to web-published reports.
  • When hovering the assets in Testlab’s UI, the hovers now show also the files attached to the assets.
  • Help-browser window can now be resized and left open while using Testlab. As previously, you can also open up the help to separate browser tab.
  • API: The responses of REST API have been enhanced in a way that attached files are also included in responses. The related objects of assets also provide HAL-compatible links now for easier navigation in the response graph.
  • Concurrent editing and testing of test cases is now handled with better and more clear warning messages. 
 

Thanking you for all your feedback,

Meliora team


Helios 2

Helios 1 and Helios 2 are probes launched in 1974 and 1975 to study solar processes. They are no longer operational but remain in their orbits around the Sun.

The probes were once fastest man-made objects at 252 792 km/h (157 078 mph) – over 6 times around the earth in an hour. That is 70.22 kilometers per second. From London to New York in 79 seconds. On the other hand, it is only 586 times faster than the fastest production car Bugatti Veyron 16.4 Super Sport. For Helios 2, It would take 18028 years to reach Alpha Centauri, the nearest star system to the Sun. With Bugatti Veyron, it would take 10.5 million years. And while driving, you would have to fill the tank 459 900 000 000 times which equals 45 263 661 534 000 liters of gasoline. If we construct a cube as a gasoline tank for the fuel, we would need a cube that is approx. 3.6 kilometers per side.

(Source: Wikipedia)

Facebooktwitterlinkedinmail


Tags for this post: announce features product release reporting screenshots 


13.10.2017

Testlab – Parallax Denigrate release

We are proud to bring you a new version of Testlab – Parallax Denigrate – with usability-related features and risk analysis reporting.

 

Custom fields for projects
Targeted filtering of tree assets

Assets organized in tree structures, such as specification related assets (requirements, test cases, and test sets, can be filtered by a search field at the top of the tree control. This makes it easy to filter into the tree the assets which you are interested in.

This search field has been enhanced in a way which enables you to target the search better. For example, for test cases, filtering with

  • “priority:critical” shows all test cases prioritized as critical,
  • “name:plane tag:customer” shows all test cases with a word “plane” in the name of the test case and with a tag “customer”.

As said, this logic works with all trees in Testlab – including the pickers which are used to select assets related when editing. The UI has also been added with an easy help on the syntax as a tooltip.

 

Comments for test results
Risk analysis reporting

Often, the people responsible for the project are asked tough questions on the status of the project or product: How well is it tested? Can we go to production? Do you think the product is in a good enough for release? The manager must basically make an educated guess with the best possible information available – often from the data in the test management tool.

Testlab has been added with a Risk Analysis report which analyzes the requirements, test cases, and issues in the project and combines the information from risk view-point as a single report. The report includes

  • requirements not marked as covered, with failing or blocking tests or requirements not tested at all – grouped by requirement risk,
  • test cases not yet marked as ready, not passed or test cases which have not been tested at all – grouped by priority and
  • issues not yet resolved or closed – grouped by severity or priority.

As a combined single report, this report provides essential information for the manager to make his decision.

 

Issue-centric testing

Features have been added to support issue-centric testing better. Previously, issues in Testlab could be linked to a test case and a test run but in this new version of Testlab, it is possible to link multiple test cases (optionally via a test run as executed tests) to a single issue. The controls while editing the issue have been changed appropriately to make it easier to link an existing issue to a test case.

New functions have also been added to better utilize these links:

  • While running tests, you can now easily add the test cases linked to an issue as executable tests to your current run. To do this, click the “Add linked test cases to this run” control via the Issues tab while running tests.
  • While running a test, you can also add a link to an existing issue by clicking the “Link to current test case” control via the Issues tab.

Note: Due to this change the REST-API model has been updated. The old format is still supported for a single link but is due to be deprecated in future releases. Please see the documentation of DefectResource-endpoint in your Swagger instance (https://yourtestlab.melioratestlab.com/api).

 

Showing results in test case tree

The controls at the bottom of the test case tree are used to highlight the test cases with testing results. In previous versions of Testlab, the controls limited you to fetching the not passing results only. The controls were designed from the re-testing and regression testing point of view.

In Parallax Denigrate, these controls were changed in a way so that you have an option to simply filter in results for test cases from your preferred viewpoint (latest results in the project, results for a milestone, for a version or for a single test run). The actual change in the UI is that you also get the results for passed test cases. This makes these controls more flexible and the use of these controls is easier in different usage scenarios.

 

Better tree-pickers

The popup controls used to pick related assets are now much easier to use:

  • The pickers now feature the same searching feature introduced earlier (see “Targeted filtering of tree assets” above). This makes finding the asset from the tree much easier.
  • When picking assets, you have an option to add or remove the selected assets from the set of current values.

 

Reporting enhancements
  • The “Do not include sums of zero” option on the requirement, test case, issue and project grouping reports now filter out sums of zeroes from both axes (“Field to report” and “Group by”). Previously, the option filtered out sums of zeroes only from “Field to report” axis.
  • When old revisions (or otherwise deprecated assets) are included in reports, the assets are now highlighted with a gray color and also, the date when the asset was revised/deprecated is shown.
  • When reporting the latest results only on “Results of run tests” report, the report now also includes the test cases not yet run.
  • “Execution status of test cases” report has been added with two new options to customize the report’s behavior (“Test cases in test runs only” and “Result for latest revision”). Please see the inline tooltip helps for these two options on this report on the logic of these options.
 
Other miscellaneous changes
  • When editing a single issue, you can save the edits without closing the window by keeping Shift-key pressed.
  • When batch editing assets in the table view, top-right corner change event notifications are no longer generated to your teammates.
  • For deprecated test cases in the list of test cases in test execution view now includes the timestamp of the deprecation (when the test case was revised or when the test case was deprecated).
  • The state of “Show events” checkbox at the top right corner is now saved and remembered between sessions.
  • Copying and pasting with keyboard shortcuts now work as expected to step editor’s pre- and post-conditions.
 

Thanking you for all your feedback,

Meliora team


Bookhouse Boys

Usenet is a distributed discussion system which enables you to read and post messages, often termed as “news”, still existing but more popular back in the days. Usenet features newsgroups on various different topics and was a popular place for discussion.

In 1996, a series (hundreds) of unexplained word puzzles were posted to different newsgroups. The title for all these posts was “Markovian Parallax Denigrate” and each post contained a series of words which cryptographers and hackers have been trying to decipher – with little success. Some theories exist but the “Markovian Parallax Denigrate” has still been referred as “The Internet’s oldest and weirdest mystery”.

(Source: Wikipedia, The Daily Dot, Last (?) existing post in Google’s archive)

Facebooktwitterlinkedinmail


Tags for this post: announce features product release reporting screenshots 


13.7.2017

Testlab – Bookhouse Boy release

To celebrate the warmth of the summer months, we are proud to release a new feature version of Testlab: Bookhouse Boy.

 

Custom fields for projects
Custom fields for projects

Just like requirements, test cases, and issues, the project asset can now also be defined with custom fields. You can find the field settings for your project asset from Testlab > Manage company … view.

When you customize the fields for your project asset these field settings will take effect in all your projects. For example, you can use these fields to track some high-level project details inside Testlab such as project deadlines, resourcing related details or something else.

For reporting out these details two new project templates have been added:

  • “List of projects” which is basically a list of project details from your Testlab instance. The project filters in projects by the criteria set and lists out project details as a listing.
  • “Project grouping” which can be used to group project data by defined fields. This report includes a bar graph for the grouped data and a listing of projects matching the set criteria.

Please note: As these two reports expose details on project level, “report.all” permission does not grant permission for these two new reports. This way, these two reports might not show up with your permission set automatically. You should adjust the role your have in your projects to include “report.projectlistreport” and “report.projectgroupingreport” to have access to these reports.

 

Comments for test results
Test result comments

Each result of the test case can now be set with a distinct comment. Earlier, test case assets themselves and also steps of executed tests could be commented.

Now as you create test runs, the test cases get bound as items in these runs. As you list out test cases in your scheduled runs in the Test execution view, there is a new column in this table for an execution comment. Note that you set the comment when you wish – You don’t have to execute the test and give it a result to include a comment: This way you can also use this comment field for some information before execution of the actual tests.

The comments for executed (or scheduled) tests are also shown in test cases’ execution history view, on related reports and on test coverage view (for tests with a result set). Also for Jenkins integration, the comments sent via the API are also set to this field, if any.

 

Report page sizing and orientation

Reports can now be rendered in different page sizes and in chosen orientation. The size of the page can be set as A4 or the larger A3 and the report can be laid out in portrait or in landscape orientation. Please experiment with these settings if you have trouble fitting all your data on your reports.

 

Reporting enhancements
  • Test case related reports now support filtering in test cases from test sets and test runs. If you filter in test cases with test runs, keep in mind, that the latest execution status of the test case is then reported against these filtered in runs.
  • “Results for run tests” report now has an option to filter in latest executed result for each test case. This way, if the same test case is included multiple times, only the latest executed results are left in on the report.
  • A project can now be set with a logo which is included in each report. You can upload the logo of your choice by editing the project details.
  • Grouping reports can now be grouped also with custom field values.

 

Progress indication

The UI now includes automatic notification on server operations that might take some time to complete. Also, most operations expected to run some time such as imports of data also support showing the progress of the operation in this notification dialog.

 
Support for new file formats

Exporting data is now possible as modern Excel-files (.xlsx). Also, reports can now be exported as .docx-files for Microsoft Word.

 

Other changes
  • The changes in the tags of the asset are now stored and included in the changes history of requirements, test cases, and issues.
  • The number of defects found -column in test execution view can now be used as a filter in the table.

 

Thanking you for all your feedback,

Meliora team


Bookhouse Boys

With Bookhouse Boy, we wish to celebrate and give homage to the true visionaries behind Twin Peaks – one of the greatest television drama series created. After 25 years, a new season of this great television is currently running offering new bizarre twists in the story of interesting characters including the small town of Twin Peaks itself. With the excellent writing of Frost and visionary directing of Lynch, the series is sure to leave it’s mark to the history of television.

All Testlab releases are code-named with some weird fact, theory, historical event or something else that should give some food for your imagination. As such, a code-name from Twin Peaks is more than fitting.

(Image from Twin Peaks (the original series) / Lynch/Frost Productions)

Facebooktwitterlinkedinmail


Tags for this post: announce features jenkins product release reporting screenshots 


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 


27.5.2014

Taking screenshots and capturing video

This article introduces you on an easy way to capture and annotate screenshots during testing. We show you couple of easy ways to use screen capturing and recording tool Monosnap.

The latest Testlab release brings you inbuilt integration to Monosnap, a handy screen capturing tool with possibility of annotating the screenshots before uploading. Testlab supports desktop clients of Monosnap for Windows and Mac OS X operating systems. You are ofcourse free to use any screen capturing tool you prefer but we feel Monosnap really stands out from the crowd feature-wise and in the ease of use.

 

Why take screenshots or record video

When you are testing software on your workstation taking screenshots is a great way of documenting issues. A picture is worth a thousand words, right ? For example, when you are testing and an issue such as a defect is encountered capturing a screenshot, annotating the capture by highlighting the issue in an exact way and uploading it to Testlab usually tells the team members very well what went wrong. If the capturing tool allows you to annotate the shot, it’s perfect – the amount of textual description you need to enter for the defect is typically much less when you can mark and highlight the relevant parts of the screenshot.

The benefits of using screenshots in issue management are quite self-evident. But screenshots and recorded screencaptures can be quite beneficial in requirement management too. For example, when you are documenting new features on existing user interfaces, taking a screenshot and annotating it properly is a great addition to documenting your requirements. Same applies to test cases: If a test case is testing a complex user interface a well annotated screenshot or two can be a great help for a tester when testing.

 

Monosnap introduced

monosnapMonosnap is a collaboration tool for taking screenshots, sharing files and recording video from your desktop. The tool is available for multiple platforms (such as a Google Chrome extension, for iPhone and iPad) but here we talk about the desktop installable clients for Microsoft Windows and Mac OS X operating systems as they can be integrated and used seamlessly with Testlab.

When Monosnap is installed and run it runs as a desktop application and is accessible in a way depending on your operating system. For Mac OS X, the tool is available in your desktop’s menu bar as an icon. Similarly in Windows, the tool is available in your so called system tray and as a hovering hotspot on your desktop if you prefer.

For capturing screenshots the basic way of working with Monosnap is as follows:

  1. You capture an area of your desktop by selecting “Capture Area” from Monosnap’s menu or pressing the appropriate keyboard shortcut.
  2. A Monosnap window appears with the captured area shown. The window has functions to annotate the capture: For example draw different shapes on it and write text on the capture.
  3. When you are happy with the capture you can upload it to a service of your choice or save the capture on your disk.

For capturing video, you

  1. select “Record Video” from monosnap’s menu or press the appropriate keyboard shortcut.
  2. Monosnap’s recording frame appears. You move and resize this frame to the area on your desktop which you would like to record as a video capture. You also have options to record video from your workstations web cam, record audio from your microphone if you prefer.
  3. To start recording you press the Rec button. You can annotate the video during recording by drawing different shapes on it. When you have recorded your video you press Rec button again to stop the capture.
  4. When recorded, the video is encoded to a MP4 format and depending on your workstation if might take a few seconds. A window appears with the encoded video in it which you can preview before uploading. You can then upload the captured video to a service of your choice or access the encoded video file on your disk. 

 

Using Monosnap with Testlab

To use Monosnap with Testlab you have two options: Take screen captures with Monosnap and upload them manually to Testlab by dragging and dropping or, integrating Monosnap to Testlab’s WebDAV interface which allows you to upload captures to Testlab with a click of a button.

 
Uploading manually

When uploading manually no pre-configuration is needed. You can use Monosnap in a way you prefer and when you have a capture ready upload it to Testlab in same way you would upload a regular file attachment. Keep in mind though, that Monosnap makes this quite easy as it features a “Drag bar” on the right hand side of the capture window. From this, you can just grab and drag the capture on your Testlab browser window and attach it to the asset open in the window just by dropping.

If dragging and dropping is not possible for some reason, as a workaround, you can ofcourse save the capture on your disk and upload it regularly to Testlab.

To see how it actually works play the video below:

video_reports

 

 

WebDAV integration

Monosnap is great in a way that it supports a possibility of uploading the captures with a click of a button to service of your choice. This enables Testlab to act as a WebDAV storage for which into the Monosnap can push the captures to. When configured, you can just push the Upload button of Monosnap and the capture is automatically uploaded to Testlab and attached to the asset open in your Testlab browser window.

To make use of this feature some pre-configuration is needed:

  1. Open up Monosnap’s menu and select “Preferences…” or “Settings…”. Monosnap’s settings window opens up.
  2. Select “General” tab and configure the following:
    • After screenshot: Open Monosnap editor
    • After upload: Do not copy
    • Open in browser: no
    • Short links: no
  3. Select the “Account / WebDAV” view and configure the following:

    For Mac OS X:

    • Host: https://COMPANY.melioratestlab.com/api/attachment/user
      Note: Replace COMPANY with the virtual host of your own Testlab. For example, if you are using hosted Testlab from mycompany.melioratestlab.com enter “https://mycompany.melioratestlab.com/api/attachment/user” to this field. For on-premise installations, set this field to match the protocol, host name and the port of your server to a /api/attachment/user context.
    • Port: Leave as blank (shows as gray “80”)
    • User: User ID of your Testlab account
    • Password: Password of your Testlab account
    • Folder: Leave as blank (shows as gray “/var/www/webdav”)
    • Base URL:Leave as blank (shows as gray “http://127.0.0.1/webdav”)
      Click “Make default” button to make the configured WebDAV service as the default upload service of Monosnap. When set, the Upload button always uses this service by default.

       

      For Microsoft Windows:

    • Host: COMPANY.melioratestlab.com
    • Note: Replace COMPANY with the virtual host of your own Testlab. For example, if you are using Testlab from mycompany.melioratestlab.com enter “mycompany.melioratestlab.com” to this field.
    • Port: HTTPS or HTTP port of your Testlab server – if you are using hosted Testlab enter 443
    • User: User ID of your Testlab account
    • Password: Password of your Testlab account
    • Directory: /api/attachment/user
    • Base URL: Leave as blank

The preconfiguration is documented in detail in the “Screenshots and recording” section of the Testlab’s integrated help manual.

Keep in mind, that the pre-configuration step needs to be done only once. Once you’ve configured your Monosnap to upload captures to Testlab it just works – no need to configure it again later.

Where is the capture uploaded to

When captures are uploaded via Testlab’s WebDAV interface the uploaded captures are automatically attached to the asset which is currently open in your Testlab browser window. So when uploading, make sure you have an asset (a requirement, a test case or an issue) open in your Testlab window in a way, that a file can be attached to it. If for example, your Testlab user account wouldn’t have proper permissions to attach files to assets the uploading will just silently fail.

To see WebDAV integrated Monosnap in action play the video below:

video_reports

 

 

Advantages gained

Having easy to use screen capture tools make your documenting easier and speeds up work in multiple tiers: Documenting issues and other assets is faster and people dealing with the documented assets have a clearer understanding on the issue at hand.

Facebooktwitterlinkedinmail


Tags for this post: example features screenshots usage video 


25.4.2014

New features: Enhanced reporting, exploratory testing and easy screenshots

A new quarterly feature release of Testlab (codenamed Last Resort) is out! This update gives you enhanced reporting, better support for exploratory testing, easier screen and video capturing and a bunch of other enhancements. Read on.

 

video_reports

 
Enhanced reporting

Reporting in Testlab is now much better than before. You can now preconfigure report parameters and publish your reports so that they can be launched with a single click. Reports can be saved to three different scopes: to a project, to all projects or to personal use only.

  • New report view added for adding and launching reports
  • Preconfigure report parameters and publish your reports with a descriptive name (for example “Critical open issues of BETA” or “Last month testing activity”)
  • Save reports to your project, to all your projects or as private report just for you.
  • Launch your reports with a single click
  • Time bound reports such as progress reports can be configured with relative dates. For example, you can configure a testing progress report to always be reported from start of the current month to current day. Generating a monthly progress report this way is just a click away.
  • New report type added: Testing activity. This reports a summary of all testing activities performed during a time frame or for a set of versions including executed tests and updated assets such as issues, requirements or test cases.
  • Listing reports now include all configured custom fields and comments.
  • All reports now take into account the project’s time zone and user’s locale for date and time formatting.
  • Testlab’s search function also looks up published reports.

 

video_exploratory_testing

 
Exploratory testing

Pre-planning your testing and test cases is not always possible or desirable. Exploratory testing is an approach to testing where the tester or team of testers ‘explores’ the system under test and during the testing generates and documents good test cases to be run.

This type of testing is now well supported in Testlab. It is possible to add, remove and edit test cases during execution. It is also possible to add notes or comments to test cases during execution. This can enhance communication between testers and even between different testing sessions. 

  • Add test cases to the test run during a testing session.
  • Remove test cases during a testing session.
  • Edit existing test cases and their steps during execution.
  • Comment test cases during execution and have access to comments entered for test cases’ steps on previous runs.
  • Execute test cases in any order by jumping between sessions’ test cases.

All new functions are implemented in a way that they available to all testing approaches.

 

video_verify_track_and_report

 
Capturing screenshots and video

Testlab integrates with Monosnap, a powerful screenshot tool, allowing you to easily capture and annotate screenshots. You can also record a screencast or video. Testlab offers an interface to Monosnap so that you can add the content to Testlab with a click of a Upload button. Alternatively, you can just drag-and-drop captured content from Monosnap to attach it easily to Testlab’s asset.

Captured content is uploaded in a secure way directly to Testlab and stored as file attachment to your project asset.

  • Capture screenshots and annotate them – great way to highlight any issues.
  • Easy and fast.
  • Record video and upload MP4 encoded screencast to Testlab.
  • Integration supports the desktop client of Monosnap for Windows and Mac OS X.

 

Other enhancements

In addition to major features described above, the version includes enhancements such as:

  • Test cases can be easily executed directly from the test hierarchy tree context menu. In addition to this, the issue view enables you to easily run the test case the issue is related to – handy, when you just want to re-test and verify if the issue is really fixed or not.
  • Attached images are shown directly in UI by hovering on them with your mouse cursor.
  • When adding a new test run the dialog now features “Save and start …” button to start executing with the new test run immediately.
  • Major performance enhancements in situation when the project has a huge number of executed tests or test runs.

 

Sincerely yours,

Meliora team


letterOn every British nuclear submarine, there is a safe. Inside that safe is another safe. And inside that safe is a handwritten letter from the British Prime Minister, to be opened only if the country has been decimated by nuclear war.” (This American Life, episode 399).

United Kingdom’s nuclear doctrine is unique in a way that each Prime Minister can decide the orders for the nuclear submarines in the event that the British government has been incapacitated by a nuclear strike. These orders are handwritten by the Prime Minister, placed in a safe on each submarine and are destroyed unopened after the Prime Minister leaves office. What action each Prime Minister would have ordered is only ever known to the outgoing Prime Minister. If the orders were ever to be carried out, the action taken would be the last official act of Her Majesty’s Government.

 

Facebooktwitterlinkedinmail


Tags for this post: announce exploratory features release reporting screenshots 


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