Posts tagged with: video


Meliora Testlab – Polybius – released

Meliora Testlab team is proud to announce a new version of Testlab – Polybius. In addition to smaller enhancements many of the new features revolve around parameterization of test cases. It is now possible to create test cases as templates and when executing them, enter the parameters of the template to easily create variants of the test case.

Please read more about the new features and changes below. 


Test case parameters

Test case templating with parameters

Test cases can now be embedded with parameters. Parameters are basicly tags entered to test cases’ description, preconditions, steps or to the expected end result. In the content text, parameters should be entered as


When test case is entered with parameter values later on, the actual description shown to the tester will include parameter tags replaced with entered values.

Using parameters is an easy way to create many executable variants for a test case with similar description content. For example, if you have a set of test cases intended to be run with each different web browser variant, you can describe your test case with a appropriate ${BROWSER} tag. This way you can easily plan & execute this test case for different web browsers by entering fitting values for this parameter later on.


Parameter typing

Testlab includes a management view for all project’s parameters. You can configure your parameters as selection lists, which restricts the values that can be selected for these parameters.


Planning and running tests with parameters

To create test case variants for parameterized test cases you can now enter values for the parameters in Execution planning view. The editor features a column showing all possible parameters for the test case and allows you to enter values for them. When a parameterized test case (template) is added to a test set and it is set with parameter values, the test case becomes a parameterized instance to be run.

Test execution view has similar controls where you can enter parameter values for test cases already added to a test run.


Issue management enhancements
  • Issue is added with a new field “Found with parameters” which always includes the parameters of the test case the issue was added for (if any).
  • The issue listing includes a similar field as a column which allows you to easily filter in issues with specific parameter value.
  • When adding a new issue while executing a test case, the failed steps and their comments so far are now automatically copied to the issue’s description field.


Coverage and reporting with parameterized tests

Test coverage view with coverage views via requirements and test cases have been enhanced to include parameterized test cases. Each parameterized variant of a test case is now calculated as a single verifying test case in the coverage calculation. The view also shows the parameters the test cases were run with.

The reports also now include the test case parameters in appropriate places (Issue listing, requirement coverage, results of run tests and execution status of test cases report). Issue listing, results of run tests and execution status of test cases reports also have test case parameter values as filters which allows you to filter in specific results from your test runs.


Jenkins plugin changes

Meliora Testlab Jenkins plugin now supports passing test case parameters from Jenkins’ environmental variables. You can list the variables which are passed as they are with the results and will be included as parameters at Testlab side.

For example, test case(s) in your Testlab project might have a parameter titled ${BROWSER}. When running automated UI tests in your Jenkins, enter a value “BROWSER” to this new setting and ensure that your Jenkins job sets an environmental variable BROWSER to some sensible value. This way running the job sends and sets the ${BROWSER} test case parameter value to all run tests to a value matching to the environmental variable.


Importing test runs

A CSV import of test runs has been added. Importing test runs supports importing test run details, test cases run in them and testing results of test cases and their steps.


Centralized authentication (CAS) improvements

Registration of new user accounts

Previously, when users authenticated via an external source via CAS came into Testlab, if they had not yet been created with Testlab user account, they could not log on. This is because authorization to Testlab’s projects are done via Testlab’s user accounts the needed roles and permissions must be granted to these users for the access.

This version is improved in a way, that when a user without Testlab account gets authenticated via CAS, he/she is shown with a welcome screen allowing her to register a personal Testlab account by entering few details (e-mail address, full name). The Testlab user account is then automatically created and an e-mail messages is sent to the company administrators notifying them about the new account.

Granting roles to new accounts (Onpremise)

On-premise version of Testlab can be configured to automatically grant a set of roles in a set of projects when a new user account is registered via CAS.

Relaxing the SSL verification of the host name for ticket validations

When setting up CAS, the client can now be configured to skip the host name check of the SSL certificate when verifying CAS tickets. This may help setting up CAS with self-signed certificates or with proxy configurations.


Sincerely yours,

Meliora team


Fancy a game ? Polybius is an arcade game which is said to have induced various psychological effects on players. The story describes players suffering from amnesia, night terrors, and a tendency to stop playing all video games. Around a month after its supposed release in 1981, Polybius is said to have disappeared without a trace. [Wikipedia]

In the span of a week, three children really did fall ill upon playing video games at arcades in the Portland area. Michael Lopez got a migraine, the first he’d ever had, from playing Tempest. Brian Mauro, a 12-year-old trying to set the world record for playing Asteroids for the longest time, fell ill after a 28-hour stint. And only a week later 18-year-old competitive gamer Jeff Dailey died due to a heart attack after chasing the world record in Berserk. One year later 19-year-old Peter Burkowski followed suit for the same reason playing the same game. [Eurogamer]

(Photo by DocAtRS [CC BY-SA 3.0], via Wikimedia Commons)




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


Testlab – Flannan Isles released

Summer is here! We’re happy to announce a new feature release of Testlab: Flannan Isles. The version has a number of new features and user interface enhancements described in detail below. As expected, all features are immediately available for all our hosted users. Enjoy! 



Tagging assets

Ever had a situation where you’d like to pin some data in your system of choice to find it later on or, group it up with similar data ? This is now possible in Testlab as it implements tagging of assets where you can pin your assets with keywords of your choice.

  • Tag requirements, test cases, test sets, test runs, issues and reports
  • Easy tagging of single assets
  • Tag multiple assets by selecting your assets from a tree or, tag multiple issues using issue listing filtering
  • Easy to use project tag cloud – click a tag to search content by your tag. Or search manually by entering a search word in format “tag:your tag”.
  • Filter tree content by searching with “tag:your tag”
  • Reporting and coverage analysis now support filtering with tags

Tagging assets is especially useful in situations, where you have a need to group some of your assets for later use. For example, you might want to tag all your requirements targeted for future release for easier management of your next release.



Direct editing of requirements and test cases

The views for managing the central assets of Testlab, requirements and test cases, have been enhanced with more snappy direct editing mode.

In previous Testlab versions we had separate viewing of assets and a transition to an editing mode. From now on, the forms and controls on requirement and test case editing are always editable with just a click for everyone with needed permissions.

In addition, the form controls have now a more clear disabled look to indicate what is editable and what is not.



Control and monitor automated tests

Dashboard of Testlab now features a new widget Jenkins Jobs which enables you to monitor and trigger jobs in your Jenkins CI server.

  • View your jobs’ build trend, latest build result and build number directly on your Testlab dashboard
  • Launch builds directly from the widget
  • Open up the related views on your browser from your Jenkins server with just a click
  • Pick the jobs you prefer – even from multiple different Jenkins servers if needed. Up to four different Jenkins servers can be controlled from a single dashboard.
  • Easy UI – if you are familiar with Jenkins’ UI you feel at home with this one
  • Integrates directly from your browser utilizing the Jenkins’ Meliora Testlab plugin at your Jenkins server


Reporting enhancements

The reports of Testlab have been enhanced with following addition:

  • New filtering options added for
    • Listing of requirements: covered & assignee
    • Listing of test cases: status & priority & assignee
    • Listing of issues: resolution & environment & related test case & resolved in version
  • Issues per priority report has been added with a sub report listing all issues counted to the totals
  • Similarly, execution status of test cases now includes a list of related test cases


Regenerating requirement identifiers

Requirement management now has a feature in the menu to regenerate IDs. During design, this can be used to easily regenerate all IDs in some folder or even for entire project. The identifiers will be regenerated in 1, 1.1, 1.1.1, 1.1.2, 1.1.3, … format prefixed with the same prefix as in the selected folder. If IDs are regenerated for the whole project the identifiers will be prefixed with project’s key.

Keep in mind, that regenerating IDs will overwrite and possibly change the current IDs – so use this feature sparingly.


Sincerely yours,

Meliora team


The Flannan Isles are a small island group close to Scotland, west of the Isle of Lewis. In December 1900, three men occuping the lighthouse vanished, leaving behind an unfinished meal and a mystery that’s never been conclusively solved.

The only sign of anything amiss in the lighthouse was an overturned chair by the kitchen table. No sign of the three men was found, either inside the lighthouse or anywhere on the island. Many rumours of their disappearance surfaced, from a murder to sea serpent eating the men and to foreign spies abducting them, but no conclusive evidence was never found in the investigations.

Photo by Marc Calhoun from



Tags for this post: announce features jenkins release reporting video 


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:




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:
      Note: Replace COMPANY with the virtual host of your own Testlab. For example, if you are using hosted Testlab from enter “” 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 “”)
      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:
    • Note: Replace COMPANY with the virtual host of your own Testlab. For example, if you are using Testlab from enter “” 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:




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.


Tags for this post: example features screenshots usage video 


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!



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.


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.


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.



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!



Tags for this post: announce features jenkins jira release video 


Introduction video

Today, we’re happy to bring you a brief introduction screencast about Testlab. The video will introduce you to the central concepts of Testlab and how they are presented in the user interface. We will give a glance to

  • requirements management,
  • test case design,
  • execution planning and test runs,
  • issue management and
  • test coverage.

Keep in mind that this introduction skips some central features of Testlab such as reporting but should give you some insight to the use of Testlab. To view the introduction please click below.


Introduction to Meliora Testlab


Tags for this post: demo example screencast usage video 

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