Category Archives for "Announcements"

1 JIRA 6 plugin for two-way integration with Test Collab

Many of you asked for it, so here it is. We are sorry for a little delay in this release – but now it is here and ready to use. Visit Downloads page.
For those of you who missed our little demo on two-way integration, please take a look at our previous blog post on Two-way integration. Note that we have used Redmine to prepare a video demonstration, same features and functionality is available on JIRA 5 and 6 versions.
We hope you’ll like this release and as always for any support, queries and feedback – feel free.


Test Automation for Windows and Linux

Imagine being able to track your manual and automated test results from a same place. Sounds cool right? With Test Collab not only you can do exactly that but also assign tests to human or machine with just a few clicks without messing up with a dozen APIs or doing custom code. The bottom line is:

  1. You create test and store them in your test case manager so other team members can run it.
  2. Few of these tests are automated too.
  3. But there is no easy way to keep track of automated results for each test. Okay, maybe your build server does that but then again you have to check test results at two different places: Test Case manager for manual test and Build server for automated test.
  4. And to run manual test, you will assign an execution to your team. Similarly you will trigger a new build on your build server for running automated tests.


    We know this is unproductive so we bring you our new improved remote executor.

For people who never read about remote executors yet, here’s a quick summary: Test Collab Remote Executor turns your machine into a test slave which is used to run automated tests. It posts all necessary info produced while testing to Test Collab server for analysis. Check the how-to screen cast here (little outdated) – it isn’t best explanation but will help you in a basic way. For further help, you can always reach our support team.

While we launched this quite a while back, but now we revamped the whole thing and added support for linux platform too. This is first stable release of our remote executor. Download here


Test Collab 1.2 launched with new deployment options: VirtualBox and middleware package

With the current release 1.2, we introduce trial version for self hosted in middleware and Virtual machine format. So far trial was available only on our hosted platform, but now you can try Test Collab on your own infrastructure for 30 days. To choose right package for you, please go to our new trial page.

Apart from that we’ve introduced some new features and bug fixes. Here’s the complete change log:




Hierarchy of Test Suites not shown correctly on test case add page




Multiple user integration not documented





Document jira custom fields integration process





Deleted Execution’s name missing on activity on production





In production, attachments are always private irrespective of settings




No permission for requirement





Incomplete info on activities





‘Filter By Requirements’ did not work for limited rights user





Tracability Matrix could be seen even when user had ‘No Access’ to requirements module




Automatic redirection to the requested page after user has logged in




Names of deleted milestones and executions not shown in activity list




Custom field not shown with issue created on JIRA





Warnings related to resources especially Images





Suites drop down’s structure on upload CSV page





Suite name same as deleted suite is not allowed





Suite not shown expanded, when its case was being viewed while navigating on suites dashboard




Editing a test or a suite makes it last child of its parent suite.





Changing suite of a test cases doesn’t update sort order on test case




Breadcrumb missing on milestone view page





Ability to send emails to all administrator





Copy test case functionality


Screencast: Test Automation with Test Collab

Ok first things first: What’s the main problem with most test automation techniques are: they do not offer very well interface, so you don’t have a good workflow around them in order to execute and extract meaningful information from them, most of time these tests end up being forgotten in build process or gets too old with time without ever being updated. Nor are they integrated well around your manual testing process. Writing automated test case is too damn easy, but difficult part is collecting insights and meaningful data from them over time. See this screencast and find out how Test Collab can solve your test automation worries: (small note: this is my first screencast, so please excuse bad voice quality)

To enable this feature in your account, go to Settings > General Settings, then check ‘Enable Test Automation’ and hit ‘Save’. Refresh once to see the ‘Remote Executors’ link under ‘Settings’ tab.

Multiple user integration with your issue manager now possible!

Till now it was possible to integrate single user of your issue manager with Test Collab profile. So it wasn’t possible to know which user actually reported that failure by looking at the defect in your issue manager, since the API was using a single user’s credentials. This week we have released a new feature which will let all your team members have their own credentials stored with Test Collab, so that when they report a new failure, the reporter(in your defect manager) would be automatically shown as the person who actually executed that test.

To configure this feature, simply follow these steps:

  1. Login to your account, then go to edit profile

  2. You will notice a link on bottom of this edit profile page, which goes something this:
  3. Clicking that link will take you to the page where you can specify your login credentials for your issue manager profile. These credentials will be stored with your Test Collab profile. Fields displayed on this page depends on the type of issue manager you use. Some issue managers like JIRA, Fogbugz and others do not require an API key, rather they need username and password. It will show you username and password automatically if that’s the case.
  4. After clicking the ‘link account’ button you should see a message like ‘credentials stored successfully’. That means your issue manager account is now linked with your Test Collab profile.

Please note: this feature does not validate specified issue manager credentials, unlike our integration process. That means you’ll have two make sure you enter correct credentials otherwise new issues won’t be created when this user tries reporting a test failure. If some user’s profile is not linked to the issue manager, then the default user will be used as a reporter to report the defect. The default user is one which you have configured on issue manager integration page. As an administrator you can also go to user’s index and link their profiles one by one.

Thanks to Amy Wan of Graph Net Health for reporting this enhancement. We hope you’ll enjoy this new feature. Thanks for reading the post.

Start of our Test Case Management software

Not too long ago, we realized that we don’t have a very efficient testing procedure in place along with our release cycles. We were infact doing worst at testing when compared to other processes. The problems were:

1. Testing was done by testers in isolation and reporting was terrible manual using spreadsheets. There was nothing concrete which we could refer as “Test Execution report”.

Continue reading