Test Collab » Announcements

Test Collab 1.2 launched!

Abhimanyu Grover — Tue, 21 May 2013 05:08:11 +0000

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

Abhimanyu Grover — Fri, 09 Dec 2011 21:07:33 +0000

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!

Abhimanyu Grover — Mon, 28 Nov 2011 11:47:18 +0000

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:

Login to your account, then go to edit profile
You will notice a link on bottom of this edit profile page, which goes something this:
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.
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

Abhimanyu Grover — Wed, 05 Jan 2011 06:46:13 +0000

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

2. Unless there was a major visible test failure, no one in the team cared about results.

3. Releases were delayed many times because of last minute test failures.

4. And as a famous book Pragmatic Programmer says:

Design to Test
Start thinking about testing before you write a line of code.

We were not following that very well even when we wanted to. Guess why? Because there was no space where we could keep throwing list of our test cases.

That was the time when we realized that we really needed to fill this gap in order to improve our software quality, and that is when we began looking for a test case management software which would fit in our needs. After trying several softwares, we concluded that not a single software was meant for us. Out of 7-8 softwares we tried, we found out 50% of them were old school and are no more suitable for “agile methodology”, others were either too closed to customize with our internal process, or were too terrible at reporting/collaboration, or were too expensive for a small business like us. So we decided to develop one ourselves focusing on agility and something which could be easily integrated with your existing processes easily.