Thanks to the guys at Pivotal Tracker and all our customers for the support.
Test Collab v1.12 released: Introducing Test Plans, Improved Requirements Management and coverage reports
We’re proud to announce our latest release Test Collab v1.12, which introduces Test Plans, an in-built requirements management engine, new coverage reports: for entire project, version-wise and module-wise and several enhancements and bug fixes.
You can now contain multiple test executions under one entity, i.e., test plan. Besides acting as a parent for multiple test executions, you can also use test plans to mix-and-combine multiple configuration values for creating multiple test executions. Consider this example:
You have one web app that needs to be tested with browsers: IE, Chrome and Firefox on OS: Ubuntu and Windows.
With Test Plans you’ll just select the configurations and cases to execute, it’ll automatically create multiple 3 x 2 = 6 test executions.
Learn more about Test Plans.
So far you only had an option to use external sources or your issue manager as requirements engine, but this limited many of you to do things. So we decide to make our own requirements manager. You can create requirements in form of features and scenarios, contain them in versions or group them in modules. You can also track coverage report for requirements project-wise, version-wise of component-wise.
Managing Versions and Modules
Both these features open up a lot of possibilities for teams. Stay tuned on our blog for upcoming detailed examples and how-tos.
During your application life cycle a lot of new changes are made to existing features, and when these features change, so does your test cases. Do you know Test Collab stores all revisions of your test case? So every time you make a change in your test case, the old revision is automatically stored. This means you can keep track of such changes over time.
At times this information can be of great help, say, you are a test engineer and you are looking at the executions from 3 months back for ’Feature A’, and you want to know how exactly this test case was executed back then. But there have been a lot of improvements in ’Feature A’ in your application in last 3 months, and so obviously test cases associated with that feature are also changed several times.
Test Collab will take care of such scenarios by automatic versioning of all your test cases and storing each revision. It will also store reference of the test case’s revision # which was executed, so you can view the same.
Creating same kind of test executions is a hassle, especially when you find yourself selecting same set of cases again and again. Test Collab introduces a feature of Execution Templates with this release, and as the name suggests, based on these templates new Test Executions can be created quickly.
Test execution creation process requires the user to select the set of suites having the test cases that he wants to be executed and the tester who will be responsible to execute them. This is quite simple and straightforward process, but what if the user has to create the test executions with same set of test suites to be assigned to the same group of testers, at the time of every product release (say for regressions tests or integration tests) ? Execution templates come handy at the times where the similar kind of assignment process is to be repeated time and again.
With execution templates you can now have one or more test case selection criteria defined on the basis of test suites and / or tags. Each criterion can have one or more testers selected for it.
Once an execution template is defined, new test executions can be created on its basis and they will automatically have test cases matching the selection criteria defined. All desired test cases will also get automatically assigned to designated testers.
More details on the feature are available here.
Today we’ve released Pivotal Tracker integration with Test Collab. Pivotal tracker is lightweight, agile project management tool for software teams. See Integration guide for more details.
It has been a long time since PHP 5.3 was declared unsupported, while we continued to support it at Test Collab.
Test Collab version 1.8.2 will be our last release to support PHP 5.3. Our next releases 1.9.0 and onwards will no longer support PHP 5.3 and will need at least PHP 5.4 or onwards to run properly.
We just released new test case distribution report. It’ll be available under Project Menu > Reports
With effect from 15th June, 2015 – the prices for self-hosted versions will be revised from $150/user to $200/user. Unlimited user license will be revised from $8000 to $9500.
Save big on self-hosted license if you decide to buy before 15th June.
Currently our test execution popup works well for many teams where sequential-execution is a must. But it has a drawback: flexibility.
Many teams need flexibility in their testing without enforcing order of test cases execution. We’ve now made such a scenario possible with new execution interface. So, instead of popup, your test case information is displayed side-by-side as test cases tree list. This means, you can jump to any test case or suite in middle of execution and come back to test case where you left, very easily.
This feature is currently alpha and is available on request while we collect more feedback from users. It will be available as configurable option on all instances soon.
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.
First two changes are to be implemented immediately within 48 hours.
Once again, we apologize for this inconvenience.