Announcements

Jan 14, 2015: Unpexpected outages in last 24 hours

Announcements No Comments

First off, we apologize to all our hosted customers for two consecutive outages in last 24 hours which resulted in downtime of 15 minutes and 60 minutes respectively.

What went wrong?
Our billing server had an unexpected issues at data center which required a manual restart – this should have been simple enough. But due to some issue, server was stuck while restart operation. Although the application server (HTTP Server + DB) was running all the time during both outages, it interacts with billing server – and when it failed to do so, many of you saw following error:
“Plan for this account has been expired. Contact your account owner”

What we’re doing to avoid this in future?
Note: As much as I’d like to put this in simple words but if you’re not a web expert you might not understand this part but we’d still like to keep things transparent with all of you.

  • Response from billing server will be cached for longer time period – so downtime on billing server won’t affect the application functioning.
  • DNS Cache times will be increased, so any failure on DNS servers won’t affect application accessibility for those with almost expiring DNS cache records.
  • We’re also considering new options to communicate with our customers during downtime.
  • First two changes are to be implemented immediately within 48 hours.

    Once again, we apologize for this inconvenience.

    Test Collab 1.6 released: Assembla and Github Integrations, Execution reports and more

    Announcements No Comments

    We are proud to announce the release of Test Collab 1.6 today with several important features and enhancements.

    Asembla & Github integrations
    Now you can link Test Collab with Asembla & Github issue managers.
    Assembla Integration Guide, Github Integration Guide

    Execution Report
    Create customized reports, view trends of your test data along with many important test metrics.

    JIRA REST API Integration

    New User Interface

    Requirements management feature is out of beta with many improvements

    Test Collab 1.5 launched, introducing Test Case versioning, Active directory integration and custom fields for test cases

    Announcements No Comments

    We are happy to announce the release of Test Collab v1.5. This version introduces Test Case versioning, Active directory integration and custom fields for test cases. Complete changelog of 1.5 is as follows:

    #6007 Feature: Executor name should be shown on test case index of bi-integration panel
    #5959 Bug: CSV Export has issues with special characters
    #5943 Feature: Encrypt external passwords and api keys before storing in database
    #5942 Feature: Test case versioning of custom fields
    #5915 Bug: Autocomplete for suite dashboard and execution assign fails if regular expression special characters are present
    #5900 Feature: Revision note field on test case edit form
    #5840 Feature: Test case versioning
    #4641 Feature: Execution start and end timestamps
    #3366 Feature: View own execution permission
    #3306 Feature: LDAP and Active directory integration for user authentication
    #2958 Requirement: Custom fields for test cases
    #2897 Requirement: How a role assigned to a user can be changed?
    #2704 Bug: Order of test cases in Tracibility matrix
    #3848 Feature: Xml import of test cases and suites
    #4605 Bug: Editing project level test automation settings (parameters) aren’t reflected immediately on ‘test automate’ page
    #5056 Bug: All tags cannot be removed from a test case
    #4543 Bug: If there are no test suites and cases in a project then clicking Search or Reset buttons on suites manage redirect me to project’s dashboard
    #4511 Bug: Checkbox are shown on all columns of tree
    #3459 Bug: At the time of editing a test execution, related (though archived) milestone should be shown selected
    #1944 Bug: user should not be able to delete a role which is already assigned to some users
    #5774 Feature: Improve import processing screen
    #5727 Feature: Suite Hierarchy structure on copy from other project
    #5567 Feature: Unfuddle custom fields with select type and their option ids
    #5021 Feature: Change all flash charts to JS
    #4800 Feature: Test run templates
    #4617 Feature: Implement new responsive select list on export page
    #4353 Feature: Improve import from other project
    #4316 Feature: Reusable steps after import (copy) should expand as separate steps
    #4027 Feature: Option to copy test suite
    #5250 Enhancement: ajax url should be independent of siteUrl in the config
    #2957 Requirement: Export execution report
    #4618 Enhancement: Suites dashboard state should be sharable.
    #4520 Enhancement: Automatically set the selected suite as parent when redirecting to add test case page from suites manage page
    #4519 Enhancement: Auto complete on suites combo on add test case
    #4476 Enhancement: Sorted tree structure for suites selection for various pages
    #4475 Enhancement: Sorted tree structure for suites on Export page
    #4462 Enhancement: When a limited rights user is to be shown “No Access” message, can we redirect him to last used (referer) page in place of the dashboard or project’s overview page ?
    #4444 Enhancement: Better responsive select box for large list
    #3635 Enhancement: Title of newly copied test case should be unqiue
    #3927 Feature: Automatic redirection to the requested page after user has logged in

    JIRA 6 plugin for two-way integration with Test Collab

    Announcements 1 Comment

    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

    Announcements,Testing Tips 3 Comments

    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!

    Announcements 1 Comment

    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:

    4397

    Bug

       

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

    4358

    Documentation

     

    Multiple user integration not documented

       

    4331

    Documentation

     

    Document jira custom fields integration process

       

    4024

    Bug

       

    Deleted Execution’s name missing on activity on production

     

    4023

    Bug

       

    In production, attachments are always private irrespective of settings

    3983

    Bug

       

    No permission for requirement

         

    3981

    Bug

       

    Incomplete info on activities

           

    3979

    Bug

       

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

     

    3975

    Bug

       

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

    3927

    Feature

       

    Automatic redirection to the requested page after user has logged in

    3913

    Bug

       

    Names of deleted milestones and executions not shown in activity list

    3845

    Bug

       

    Custom field not shown with issue created on JIRA

       

    3809

    Bug

       

    Warnings related to resources especially Images

       

    3807

    Enhancement

     

    Suites drop down’s structure on upload CSV page

       

    3804

    Bug

       

    Suite name same as deleted suite is not allowed

       

    3664

    Bug

       

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

    3643

    Bug

       

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

     

    3642

    Bug

       

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

    3580

    Bug

       

    Breadcrumb missing on milestone view page

       

    3549

    Feature

       

    Ability to send emails to all administrator

       

    3305

    Feature

       

    Copy test case functionality

    Screencast: Test Automation with Test Collab

    Announcements,Testing Tips 9 Comments

    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!

    Announcements No Comments

    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

    Announcements No Comments

    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”.

    (more…)